Re: push.default=upstream doesn't play nicely with remote.pushdefault/branch.*.pushremote

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

 



On Tue, Sep 10, 2013 at 8:10 AM, Ximin Luo <infinity0@xxxxxxx> wrote:
> (Please CC me as I am not subscribed.)

No need to say that, Git mailing list is sane and doesn't do reply-to munging.

> The question here then is, what remote branch should git push to - since pushremote only specifies a repo? I can suggest two options:
>
> - A: push to branch.*.merge if it's defined; otherwise push to <current branch> (like push.default=current)
> - B: push to <current branch> regardless

Or C: introduce the concept of a publish branch to complement pushremote:

http://article.gmane.org/gmane.comp.version-control.git/233572

-- 
Felipe Contreras
--
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]