Re: Adding a new file to all git branches

On Tue, Mar 24, 2009 at 09:11:15AM +0530, Aneesh Bhasin wrote:

Not really.

You basically have three options:

 1. branch a new "README" line of development from some common ancestor
    of all branches, add the README, and then merge this new branch into
    your other branches

    The advantage of this approach is that you could actually keep the
    README branch around, making changes to it and merging it back into
    your other branches as appropriate.

    Of course, you asked about avoiding "checkout", and you will still
    have to checkout each branch to do the merge.

 2. For a one-off addition of such a README, it is probably simpler to
    just use a for loop with checkout:

      for i in branch1 branch2 branch3; do
        git checkout $i &&
        cp /path/to/README . &&
        git add README &&
        git commit -m 'add README'
      done

     Which again, obviously does checkout, but at least it's
     non-interactive. The biggest downside is that doing a full checkout
     between branches might be slow.

 3. You could also just iterate over the branches with plumbing, adding
    the README to each tree. Something like:

      hash=`git hash-object -w /path/to/README`
      for i in b1 b2 b3; do
        GIT_INDEX_FILE=index.$i; export GIT_INDEX_FILE
        git read-tree $i &&
        git update-index --add --cacheinfo 100644 $hash README &&
        tree=$(git write-tree) &&
        parent=$(git rev-parse $i) &&
        commit=$(echo added README | git commit-tree $tree -p $parent) &&
        git update-ref -m "commit: added README" refs/heads/$i $commit $parent
        rm $GIT_INDEX_FILE
        sleep 1
      done

    This is going to be faster, but obviously is much more complicated.

For a one-off addition, I would probably just do (2).

-Peff