From: Jonathan Nieder <jrnieder@gmail.com>
To: Simon Richter <sjr@debian.org>
Cc: git@vger.kernel.org, Scott Chacon <schacon@gmail.com>,
Jeff King <peff@peff.net>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: git: please refuse push containing commits marked for autosquash by default
Date: Fri, 16 Jul 2010 14:04:32 -0500 [thread overview]
Message-ID: <20100716190432.GA16371@burratino> (raw)
In-Reply-To: <20100716123715.16356.65888.reportbug@richter>
Hi Simon,
Simon Richter wrote:
> When using the --autosquash feature, quite a number of temporary commits
> are created that should never be pushed anywhere. It might be a good
> idea to have an option to refuse to transfer commits whose messages
> start with "fixup!" or "squash!", both on the server and client side.
At first glance this looks very useful, as an optional hook rather
than on by default[1].
It sounds like a good use for hooks.
Receiving side: an update hook should do the trick. See the githooks
manual page, or /usr/share/doc/git/contrib/hooks/update-paranoid for
an example.
Sending side: there is no pre-push hook yet, but there was some work
towards that about a year and a half ago[2]. Maybe someone interested
could revive the topic or figure out what remains to be done.
Jonathan
[1] Sometimes I send works in progress from one machine to another; it
would be quite unnerving if this resulted in some puzzling message
about how I forgot to rebase first.
[2] http://thread.gmane.org/gmane.comp.version-control.git/92900
http://thread.gmane.org/gmane.comp.version-control.git/128426/focus=128433
next parent reply other threads:[~2010-07-16 19:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100716123715.16356.65888.reportbug@richter>
2010-07-16 19:04 ` Jonathan Nieder [this message]
2010-07-26 15:50 ` git: please refuse push containing commits marked for autosquash by default 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=20100716190432.GA16371@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=schacon@gmail.com \
--cc=sjr@debian.org \
--cc=spearce@spearce.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).