Re: [RFC PATCH] push: start warning upcoming default change for push.default

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

 



On 12-03-10 01:16 AM, Michael Haggerty wrote:
> 
> I propose that the default should be even stricter: like "current", it
> would push to an branch with the same name as the current local branch,
> *but only if that branch already exists on the remote*.  It would only
> be possible to create a new branch on the remote by calling "git push"
> with an explicit branch argument.  I believe that such a policy would do
> the right thing in the cases where the "right thing" is pretty
> unambiguous, and would require a user decision in other cases.

I haven't thought it through very deeply, but at first glance this seems like
reasonable default behaviour to me.

		M.
--
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]