Re: [PATCH] Switch receive.denyCurrentBranch to "refuse"
- From
Jay Soffian <jaysoffian@gmail.com>
- Date
- Jan 30, 2009, 01:28 UTC
- Message-ID
- <76718490901291728y2edb0520ie87de783a43c408d@mail.gmail.com>
- In-Reply-To
- <alpine.DEB.1.00.0901300133070.3586@pacific.mpi-cbg.de>
On Thu, Jan 29, 2009 at 7:34 PM, Johannes Schindelin <johannes.schindelin@gmx.de> wrote:
> Or, the reason could be that we made a design mistake, and that the > number of puzzled new users should tell us something.
I happen to have spent some time looking at Mercurial the other day since I was curious how it's evolved since I last played with it, and so w/that perspective, I think that git did make a small design mistake. With mercurial, pull and push are symmetric opposites. Neither, by default, updates the working copy.
(Confusingly for users of both mercurial and git, the mercurial equivalent of "git pull" is "hg fetch". Doh.)
Anyway, I think that this may be what leads to confusion. git pull updates the working copy, and beginners I think expect that push, which sounds like the opposite of pull, ought do the same thing.
j.