Re: best git practices, was Re: Git User's Survey 2007 unfinished summary continued
- From
Andreas Ericsson <ae@op5.se>
- Date
- Oct 25, 2007, 07:42 UTC
- Message-ID
- <472048EB.1000707@op5.se>
- In-Reply-To
- <8fe92b430710241648j609d4d00x121836001a69d1e6@mail.gmail.com>
Jakub Narebski wrote:
Show 9 quoted lines
> On 10/24/07, Andreas Ericsson <ae@op5.se> wrote: > >> git pull. Not git push. git pull operates on one working branch >> at a time (by default), whereas git push uploads and fast-forwards >> all the common branches (by default). I want git pull to work like >> git push. > > git push is opposite (almost) to git fetch, not to git pull. >
Not to an end user that has no idea or desire to learn about git remotes or anything else. They see "ok, push updates all the remote branches, but only if it's a fast-forward". They also see "righto, git pull updates all the local branches, and even merges and does other funny things", but they *don't* understand why git-pull (in their eyes) only update ONE branch that they can actually check out. From a technical standpoint, fetch and push are the same, but from the user perspective, push and pull seem much more alike.
-- Andreas Ericsson andreas.ericsson@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231