Message: previous - next
Month: December 2013

Do new git branches and tags (master->origin/master, etc.) change repo update calls?

From: "David C. Rankin" <drankinatty@...>
Date: Mon, 23 Dec 2013 11:37:21 -0600
Tim, all,

  After a hiatus, I was updating my tde repos to see how horribly screwed I am
attempting to build on Arch after their LSB and systemd changes. Pulling head I
noted several new branch and tag names. I know what they are, but they look like
they have added origin as a path component to 3.5.13-sru, etc.. Specifically, I saw:

 + 8303efe...6fd6395 master     -> origin/master  (forced update)
 * [new branch]      v3.5.13-sru -> origin/v3.5.13-sru

  So it looks like v3.5.13-sru is now origin/v3.5.13-sru. The question that
brought up was "do I need to modify any of the scripts I use that update my
local git repo to handle the 'origin/v3.5.13-sru' designation, or will the
change be handled by the .gitmodule data?

  Additionally, there were new tags noted:

   ec1d9d9..9ec64b2  master     -> origin/master
   5ae82a0..169c39a  v3.5.13-sru -> origin/v3.5.13-sru
 * [new tag]         v3.5.13.1  -> v3.5.13.1
 * [new tag]         v3.5.13.2  -> v3.5.13.2

  Same question, is there anything I would need to change in my existing
checkout scripts such as:

git submodule foreach --recursive "git checkout v3.5.13-sru"

to reflect the new branch or tag designations? Like:

git submodule foreach --recursive "git checkout origin/v3.5.13-sru"

  Also, if there are any new links or pointers for building 3.5.13 on bleeding
edge distros like Arch, I would appreciate them as well.

  What is the state of HAL requirements? I presume it is still fully required in
3.5.13, but what about 14? I will be building 3.5.13, so I'll start by checking
on the state of HAL in the Arch user repository.

  Thanks for any help you can give :)

David C. Rankin, J.D.,P.E.