* Adding a new file to all git branches
@ 2009-03-24 3:41 Aneesh Bhasin
2009-03-24 6:31 ` Jeff King
0 siblings, 1 reply; 2+ messages in thread
From: Aneesh Bhasin @ 2009-03-24 3:41 UTC (permalink / raw)
To: git
Hi,
I was wondering if it is possible to add a file to all the branches in
a repository without individually checking out each branch ?
A possible use-case for such a scenario is say I have a git repository
with various branches related to different features, versions or
bug-fixes and I want to be able to add a README file which contains
instructions/information common to all of those branches as of now
(but may diverge in future). So, do I have to checkout each branch
individually to add the same README file to all of them or is there a
direct/indirect workaround ?
Thanks for your help..
Regards,
Aneesh
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Adding a new file to all git branches
2009-03-24 3:41 Adding a new file to all git branches Aneesh Bhasin
@ 2009-03-24 6:31 ` Jeff King
0 siblings, 0 replies; 2+ messages in thread
From: Jeff King @ 2009-03-24 6:31 UTC (permalink / raw)
To: Aneesh Bhasin; +Cc: git
On Tue, Mar 24, 2009 at 09:11:15AM +0530, Aneesh Bhasin wrote:
> I was wondering if it is possible to add a file to all the branches in
> a repository without individually checking out each branch ?
>
> A possible use-case for such a scenario is say I have a git repository
> with various branches related to different features, versions or
> bug-fixes and I want to be able to add a README file which contains
> instructions/information common to all of those branches as of now
> (but may diverge in future). So, do I have to checkout each branch
> individually to add the same README file to all of them or is there a
> direct/indirect workaround ?
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-03-24 6:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-03-24 3:41 Adding a new file to all git branches Aneesh Bhasin
2009-03-24 6:31 ` Jeff King
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.