Re: git push (mis ?)behavior
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Oct 3, 2007, 16:18 UTC
- Message-ID
- <Pine.LNX.4.64.0710031718110.28395@racer.site>
- In-Reply-To
- <20071003160731.GA7113@diana.vm.bytemark.co.uk>
Hi,
On Wed, 3 Oct 2007, Karl Hasselstr?m wrote:
Show 24 quoted lines
> On 2007-10-03 16:27:49 +0100, Johannes Schindelin wrote: > > > On Wed, 3 Oct 2007, Karl Hasselstr?m wrote: > > > > > 2. "push all branches" is the default, but the user intended to > > > push only the current branch. She ends up pushing a superset > > > of what she wanted, which is not easily fixed if she can't be > > > sure that no one else has pulled from the public repo before > > > she notices what's happened. > > > > But that is not the default. Not at all. > > > > The default is to push the refs which the remote and the local side > > have _in common_. > > I know, and that's what I meant by "all branches". Sorry for the > sloppy language. > > > Maybe we should initialise the "remote.origin.push" variable to > > "completely-bogus-branchname" when you "git init --im-a-newbie"? > > I'd rather have a suboptimal default than different defaults depending > on user settings. (See also Junio's comment on that elsewhere in this > thread.)
This thread is getting painful. Lot's of "I want"s, but nobody to date came up with a solution that makes both oldtimers and newtimers happy.
Ciao, Dscho