[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Patch queue management systems
From: |
Steinar Bang |
Subject: |
Re: Patch queue management systems |
Date: |
Thu, 11 Dec 2014 09:59:28 +0100 |
User-agent: |
Gnus/5.130012 (Ma Gnus v0.12) Emacs/24.3 (windows-nt) |
>>>>> Ted Zlatanov <address@hidden>:
> It could be more fine-grained, only protecting certain branches
> (master, emacs-*, etc.). Then people can push to "username/feature"
> branches and maintainers can merge into a protected branch.
"username/feature" sounds like a good naming scheme and one that could
cut down on the inevitable clutter (implicit blame).
(and I still think having a separate feature branch git repository is a
good idea. If that repository resides on the same server and is created
with hardlinks to the real repo, it should also be cheap
disk-usage-wise, at least initially....)
- Re: Patch queue management systems, (continued)
- Re: Patch queue management systems, Dmitry Gutov, 2014/12/09
- Re: Patch queue management systems, Eli Zaretskii, 2014/12/09
- Re: Patch queue management systems, Dmitry Gutov, 2014/12/09
- Re: Patch queue management systems, Eli Zaretskii, 2014/12/09
- Re: Patch queue management systems, Dmitry Gutov, 2014/12/09
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/10
- Re: Patch queue management systems,
Steinar Bang <=
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems, Steinar Bang, 2014/12/11
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems, David Kastrup, 2014/12/11
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems, Andreas Schwab, 2014/12/11
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems, David Kastrup, 2014/12/11
- Re: Patch queue management systems, Ted Zlatanov, 2014/12/11
- Re: Patch queue management systems, David Kastrup, 2014/12/11