From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Chris Patti <cpatti@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Has anyone written a hook to block fast forward merges to a branch?
Date: Wed, 21 Mar 2012 15:32:10 -0500 [thread overview]
Message-ID: <4F6A3ACA.6050100@gmail.com> (raw)
In-Reply-To: <CAJ8P3RCQjh1ehjsihAmu8roC1aeRo=R0sN2Wm0Y4bVk=st4ivw@mail.gmail.com>
On 3/21/2012 1:22 PM, Chris Patti wrote:
> I know there are hooks out there to block various other kinds of
> change, but I was wondering if anyone had specifically ever written
> one to block fast forward merges.
>
Maybe git-merge --no-ff would also be helpful to "do what you want".
(I'm not sure why you would tell people they can't do their work really
fast or rebase to make it look like they did, but it seems that's what
you are also implying.)
v/r,
neal
next prev parent reply other threads:[~2012-03-21 20:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 18:22 Has anyone written a hook to block fast forward merges to a branch? Chris Patti
2012-03-21 18:40 ` Jeff King
2012-03-21 20:32 ` Neal Kreitzinger [this message]
2012-03-21 20:43 ` Jeff King
2012-03-21 21:14 ` Neal Kreitzinger
2012-03-21 21:22 ` Jeff King
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=4F6A3ACA.6050100@gmail.com \
--to=nkreitzinger@gmail.com \
--cc=cpatti@gmail.com \
--cc=git@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).