From: Phillip Wood <phillip.wood@talktalk.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] rebase: support --signoff with implicit rebase
Date: Thu, 15 Mar 2018 10:55:33 +0000 [thread overview]
Message-ID: <c9978ac6-ded3-592e-aa49-53172aad75bf@talktalk.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1803151112390.20700@ZVAVAG-6OXH6DA.rhebcr.pbec.zvpebfbsg.pbz>
On 15/03/18 10:18, Johannes Schindelin wrote:
> Hi Phillip,
>
> On Wed, 14 Mar 2018, Phillip Wood wrote:
>
>> diff --git a/git-rebase.sh b/git-rebase.sh
>> index b353c33d41..40301756be 100755
>> --- a/git-rebase.sh
>> +++ b/git-rebase.sh
>> @@ -459,6 +471,18 @@ then
>> git_format_patch_opt="$git_format_patch_opt --progress"
>> fi
>>
>> +if test -n "$signoff"
>> +then
>> + test "$interactive_rebase" = explicit &&
>> + die "$(gettext "error: interactive rebase does not support --signoff")"
>> + test "$type" = merge &&
>> + die "$(gettext "error: merge rebase does not support --signoff")"
>> + test -n "$preserve_merges" &&
>> + die "$(gettext "error: cannot combine '--signoff' with '--preserve-merges'")"
>> + git_am_opt="$git_am_opt $signoff"
>> + force_rebase=t
>> +fi
>
> I wonder whether we can have this change as a separate commit? Otherwise
> we would lump that change (--interactive --signoff was previously allowed
> but the --signoff was simply ignored) with the other changes...
>
> As I mentioned in my reply to Junio's comment, it'd be awesome if
> --interactive --signoff was supported (and likewise --merge --signoff),
> but it feels like an undue feature request to be dumped on you, so I'm
> fine with the patch series simply erroring out on those combinations.
I'll have a look, if it's not too much work I'll do that, it would be
nice to have --signoff better supported.
> (I don't care about --preserve-merges anymore, as everybody knows by now.)
>
> Ciao,
> Dscho
>
next prev parent reply other threads:[~2018-03-15 10:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 11:11 [PATCH 1/2] rebase: support --signoff with implicit rebase Phillip Wood
2018-03-14 11:11 ` [PATCH 2/2] rebase --root -k: fix when root commit is empty Phillip Wood
2018-03-15 10:28 ` Johannes Schindelin
2018-03-15 10:59 ` Phillip Wood
2018-03-14 17:48 ` [PATCH 1/2] rebase: support --signoff with implicit rebase Junio C Hamano
2018-03-15 10:11 ` Johannes Schindelin
2018-03-15 10:18 ` Johannes Schindelin
2018-03-15 10:55 ` Phillip Wood [this message]
2018-03-16 12:36 ` Johannes Schindelin
2018-03-20 11:10 ` [PATCH v2 0/3] rebase: extend --signoff support Phillip Wood
2018-03-20 11:10 ` [PATCH v2 1/3] " Phillip Wood
2018-03-20 11:10 ` [PATCH v2 2/3] rebase -p: error out if --signoff is given Phillip Wood
2018-03-20 11:10 ` [PATCH v2 3/3] rebase --keep-empty: always use interactive rebase Phillip Wood
2018-03-20 16:08 ` Johannes Schindelin
2018-03-20 18:44 ` Phillip Wood
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c9978ac6-ded3-592e-aa49-53172aad75bf@talktalk.net \
--to=phillip.wood@talktalk.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=phillip.wood@dunelm.org.uk \
/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 public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).