git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Daniel Harding <dharding@living180.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Aaron Schrab <aaron@schrab.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/2] Fix --rebase-merges with custom commentChar
Date: Tue, 10 Jul 2018 16:24:19 +0300	[thread overview]
Message-ID: <e8973797-fc5f-2ca5-1881-5ee66fc8279b@living180.net> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1807090936230.75@tvgsbejvaqbjf.bet>

On Mon, 09 Jul 2018 at 10:53:14 +0300, Johannes Schindelin wrote>
> On Sun, 8 Jul 2018, Daniel Harding wrote:
> 
>> I have core.commentChar set in my .gitconfig, and when I tried to run
>> git rebase -i -r, I received an error message like the following:
>>
>> error: invalid line 3: # Branch <name>
>>
>> To fix this, I updated sequencer.c to use the configured commentChar
>> for the Branch <name> comments.  I also tweaked the tests in t3430 to
>> verify todo list generation with a custom commentChar.  I'm not sure
>> if I took the right approach with that, or if it would be better to
>> add additional tests for that case, so feel free to
>> tweak/replace/ignore the second commit as appropriate.
> 
> Nothing is as powerful as an idea whose time has come. Or as a patch whose
> time has come, I guess:
> 
> https://public-inbox.org/git/20180628020414.25036-1-aaron@schrab.com/

Oops, I should have done a bit a searching before I tossed off a patch. 
Thanks Johannes for the pointer.

> AFAICT the remaining task was to send a new revision of the patch, with
> the commit message touched up, to reflect the analysis that it handles the
> `auto` setting well.
> 
> Your patch adds a regression test in addition, which is very nice.
> 
> So maybe you can coordinate with Aaron about that first patch? I really
> think that the commit message needs to explain why the `auto` setting is
> not a problem here.

Aaron, how would you like to move forward on this?  I don't want to take 
credit from you since you were the first to post the patch.  If you 
would like to post a new version of your patch with the commit message 
updated based on the feedback, I can then add my tests to go with it. 
Alternatively if you'd like me to run with this I can repost the patch 
with you as the author along with an updated commit message and my name 
in a "Commit-message-by:" line.  Let me know your thoughts.  If I don't 
hear from you in a couple of days, I'll go ahead and repost the patch as 
I described.

Thanks,

Daniel Harding

  reply	other threads:[~2018-07-10 13:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-08 18:41 [PATCH 0/2] Fix --rebase-merges with custom commentChar Daniel Harding
2018-07-08 18:41 ` [PATCH 1/2] sequencer: fix " Daniel Harding
2018-07-08 18:41 ` [PATCH 2/2] t3430: update to test " Daniel Harding
2018-07-08 21:02   ` brian m. carlson
2018-07-09  7:52     ` Johannes Schindelin
2018-07-09 16:46       ` Junio C Hamano
2018-07-09 18:22       ` Daniel Harding
2018-07-09 19:09         ` Johannes Schindelin
2018-07-09 20:05         ` Junio C Hamano
2018-07-09 18:48     ` Daniel Harding
2018-07-09 19:14       ` Johannes Schindelin
2018-07-10 12:29         ` Daniel Harding
2018-07-10 13:08           ` Johannes Schindelin
2018-07-10 13:49             ` Daniel Harding
2018-10-02 14:38               ` Johannes Schindelin
2018-07-09 23:41       ` brian m. carlson
2018-07-09  7:53 ` [PATCH 0/2] Fix --rebase-merges " Johannes Schindelin
2018-07-10 13:24   ` Daniel Harding [this message]
2018-07-12  3:02     ` Aaron Schrab
2018-07-12 17:15       ` Junio C Hamano
2018-07-16  4:59         ` [PATCH v3] sequencer: use configured comment character Aaron Schrab
2018-07-16 15:59           ` Johannes Schindelin
2018-07-16 18:49             ` Daniel Harding
2018-07-17 16:46               ` Johannes Schindelin

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=e8973797-fc5f-2ca5-1881-5ee66fc8279b@living180.net \
    --to=dharding@living180.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=aaron@schrab.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.
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).