[git-users] Re: Merging workflow

2010-08-15 Thread garyo
Or course, it's perfectly sensible to merge back to a common branch any bugfixes pertaining to it, but I can't get such accumulate and apply all at once approach. It seems like a quite contrived approach, whch is invented just because it could be invented, and not from a real need. My

[git-users] Re: Merging workflow

2010-08-13 Thread David Doria
Ah, so fetch is an operation on the entire repository and merge is an operation on a specific branch? So you're say that 'pull'ing each branch is not necessary because the 'fetch' in 'pull's fetch+merge is redundant. Is that correct? I also don't understand why this is a deficient approach? If

[git-users] Re: Merging workflow

2010-08-13 Thread Konstantin Khomoutov
On Aug 13, 7:37 pm, David Doria daviddo...@gmail.com wrote: Ah, so fetch is an operation on the entire repository and merge is an operation on a specific branch? So you're say that 'pull'ing each branch is not necessary because the 'fetch' in 'pull's fetch+merge is redundant. Is that correct?

[git-users] Re: Merging workflow

2010-08-12 Thread David Doria
Wow.. it was that easy. Then when I update something in Project1, I just do a |[dor...@localhost AllProjects]$ git pull origin Project1 and AllProjects is now up to date. Is there any standard way to make a script to pull from a whole bunch of projects? Or should I just make a bash script with