Re: git push (mis ?)behavior

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



El 3/10/2007, a las 17:27, Johannes Schindelin escribió:

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_.

Yes, that's already been covered in this thread, probably in the first or second post, and (at least I hope) we've all read it and take it as given.

Replace "push all branches" with "push all refs that both sides have in common", which is presumably what Karl meant, and the concerns are still there.

Maybe we should initialise the "remote.origin.push" variable to
"completely-bogus-branchname" when you "git init --im-a-newbie"?

How is this comment supposed to help in any way? Please try to think about the image you're putting across; as an relatively active and prominent contributer in the Git community you are part of the "face" of the community.

Cheers,
Wincent

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux