From: Junio C Hamano <gitster@pobox•com>
To: Stefan Beller <sbeller@google•com>
Cc: git@vger•kernel.org
Subject: Re: [PATCH] Introduce a hook to run after formatting patches
Date: Mon, 17 Nov 2014 11:20:58 -0800 [thread overview]
Message-ID: <xmqqd28ly6p1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqqlhn9y7dn.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Mon, 17 Nov 2014 11:06:12 -0800")
Junio C Hamano <gitster@pobox•com> writes:
> (I am not saying that there should be an easy way to drop cruft left
> by third-party systems such as "Change-id:" line) ...
Heh, that was "should not be", but I guess it was probably obvious.
Sorry for the noise.
next prev parent reply other threads:[~2014-11-17 19:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 0:47 [PATCH] Introduce a hook to run after formatting patches Stefan Beller
2014-11-15 10:44 ` Philip Oakley
2014-11-16 18:40 ` Junio C Hamano
2014-11-17 19:01 ` Stefan Beller
2014-11-17 19:06 ` Junio C Hamano
2014-11-17 19:20 ` Junio C Hamano [this message]
2014-11-18 6:40 ` Christian Couder
2014-11-20 23:26 ` Stefan Beller
2014-11-20 23:33 ` Junio C Hamano
2014-11-21 4:31 ` Christian Couder
2014-11-18 2:30 ` Stefan Beller
2014-11-18 17:02 ` Junio C Hamano
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=xmqqd28ly6p1.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=sbeller@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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