From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Michael Haggerty <mhagger@alum.mit.edu>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Chris Packham <judge.packham@gmail.com>,
git@vger.kernel.org
Subject: Re: [RFC/PATCH] rebase--interactive: Add "sign" command
Date: Thu, 04 Aug 2016 09:05:56 -0700 [thread overview]
Message-ID: <xmqqinvg5xjv.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160803180820.2raazmsfjavoaogo@sigill.intra.peff.net> (Jeff King's message of "Wed, 3 Aug 2016 14:08:20 -0400")
Jeff King <peff@peff.net> writes:
> On Wed, Aug 03, 2016 at 09:08:48AM -0700, Junio C Hamano wrote:
>
>> > However, I could imagine that we actually want this to be more extensible.
>> > After all, all you are doing is to introduce a new rebase -i command that
>> > does nothing else than shelling out to a command.
>>
>> Yup, I tend to agree.
>>
>> Adding "sign" feature (i.e. make it pass -S to "commit [--amend]")
>> may be a good thing, but adding "sign" command to do so is not a
>> great design.
>
> I'm not sure what you mean by "feature" here, but it reminded me of
> Michael's proposal to allow options to todo lines:
>
> http://public-inbox.org/git/530DA00E.4090402@alum.mit.edu/
>
> which would allow:
>
> pick -S 1234abcd
>
> If that's what you meant, I think it is a good idea. :)
Yes, by "feature" I meant "giving the ability to decide if the
resulting commit gets signature", which can and should be orthogonal
to the choice of using editor to reword the message when the commit
is created or "--no-edit" is passed and the original message is used
verbatim.
next prev parent reply other threads:[~2016-08-04 16:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 8:47 [RFC/PATCH] rebase--interactive: Add "sign" command Chris Packham
2016-08-03 14:31 ` Johannes Schindelin
2016-08-03 15:19 ` Johannes Schindelin
2016-08-03 16:08 ` Junio C Hamano
2016-08-03 16:15 ` Johannes Schindelin
2016-08-03 18:08 ` Jeff King
2016-08-04 0:53 ` Chris Packham
2016-08-04 16:05 ` Junio C Hamano [this message]
2016-08-05 16:04 ` Johannes Schindelin
2016-08-04 0:41 ` Chris Packham
2016-08-03 15:58 ` 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=xmqqinvg5xjv.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=judge.packham@gmail.com \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.net \
/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 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.