Re: [PATCH] Documentation: add a planning document for the next CLI revamp
- From
Dmitry Potapov <dpotapov@gmail.com>
- Date
- Nov 4, 2008, 09:18 UTC
- Message-ID
- <20081104091800.GB24100@dpotapov.dyndns.org>
- In-Reply-To
- <1225691960.20883.41.camel@maia.lan>
On Mon, Nov 03, 2008 at 06:59:20PM +1300, Sam Vilain wrote:
> > I can see that some people want this behaviour by default; but to me > "push the current branch back to where it came from" seems like far more > a rational default for at least 90% of users.
I think it depends on one's workflow. If you use a centralized workflow as with CVS then yes, 90% cases you want to push the current branch. On the other hand, if people push their changes to the server only for review, it means that accidentally pushing more than one intended is not a big deal. The only one who does publishing to the official repository is the maintainer, and the maintainer is most likely to run some tests after merging all changes, which takes some time. So, it is rarely push the current branch, it is usually the branch that has been tested, so the name of the branch should be specified explicitly anyway.
Dmitry