From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: non-fast-forward pushes to Emacs Git repo "scratch" branches?
Date: Thu, 23 Jun 2016 10:18:12 -0400 [thread overview]
Message-ID: <87ziqcxa3f.fsf@lifelogs.com> (raw)
In-Reply-To: 871t3revii.fsf@russet.org.uk
On Mon, 20 Jun 2016 16:21:25 +0100 phillip.lord@russet.org.uk (Phillip Lord) wrote:
PL> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> Can the Emacs Git repo allow non-fast-forward pushes to "scratch/*"
>>> branches?
>>
>> No, because the non-fast-forward constraint is applied globally.
>> But you can delete a branch and then push a new branch under the same
>> name, with the same end result.
PL> It is possible to enforce this on a per branch basis. Just applying it
PL> on master and anything starting with "emacs" (for release branches)
PL> would do the trick.
PL> It would also be possible to prevent, for example, accidental deletions
PL> of emacs-25, or master as well as enforce the "don't check into emacs-25
PL> without asking" rule.
I'd be excited to see these improvements. Another is to enforce the
commit message formatting.
I don't have access to the relevant infrastructure, unfortunately. I
imagine it's a matter of modifying the receive hook scripts. Can I help
make it happen?
Thanks
Ted
prev parent reply other threads:[~2016-06-23 14:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-17 13:43 non-fast-forward pushes to Emacs Git repo "scratch" branches? Ted Zlatanov
2016-06-17 22:25 ` Stefan Monnier
2016-06-17 23:08 ` John Wiegley
2016-06-18 10:23 ` Ted Zlatanov
2016-06-20 15:21 ` Phillip Lord
2016-06-23 14:18 ` Ted Zlatanov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ziqcxa3f.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.