From: Ramsay Jones <ramsay@ramsayjones.plus.com>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] t5556: replace test_i18ngrep with a simple grep
Date: Wed, 28 Feb 2018 15:33:51 +0000 [thread overview]
Message-ID: <ffc3d3dc-6d21-4273-5362-cbf32e7e4e59@ramsayjones.plus.com> (raw)
In-Reply-To: <CAM0VKj=hbT_m21ssF+nedVDrfNiYHu8wd9mUD55mAdNgmnZSgA@mail.gmail.com>
On 28/02/18 00:42, SZEDER Gábor wrote:
> On Wed, Feb 28, 2018 at 12:47 AM, Ramsay Jones
> <ramsay@ramsayjones.plus.com> wrote:
>>
>>
>> On 27/02/18 22:05, Junio C Hamano wrote:
>>> Junio C Hamano <gitster@pobox.com> writes:
>>>
>>>> OK, somehow I had the version from Ramsay on a topic branch that was
>>>> not merged to 'pu'. Here is the replacement for 2/2 I'd be queuing.
>>>>
>>>> We'd need SZEDER to sign it off (optionally correcting mistakes in
>>>> the log message) if we are going with this solution.
>>>>
>>>> Thanks.
>>>
>>> I guess I missed Ramsay's v2 which already did this
>>>
>>> <550fb3f4-8d25-c5c4-0ecd-3a4e61ea13f4@ramsayjones.plus.com>
>>
>> Yes, and as I said in the cover letter, I wasn't too sure that
>> I had passed that patch along correctly. ;-)
>>
>>> so I'll use that version. We still want sign-off from Szeder,
>>> though.
>>
>> I would be happy with either version, or maybe Szeder would like
>> to tweak the commit message. In any event, it would be good to
>> get sign-off from Szeder.
>
> Certainly, here you go:
>
> Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Thanks!
> However, I'm not sure about the authorship and taking credit for the
> patch. We ended up taking my patch, sure, but I think Ramsay did all
> the real hard work, i.e. writing the commit message and, most
> importantly, realizing that something is wrong with that '...| sort' at
> the end of the line.
No, the patch and the credit are yours, I was just trying to
help out and get the patches moving forward. At most, I would
think a 'Helped-by:' would be sufficient to note my input.
[BTW, my 'Signed-off-by:' on that patch was in the spirit of
the dco section b. - again I wasn't quite sure ...]
ATB,
Ramsay Jones
next prev parent reply other threads:[~2018-02-28 15:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 0:18 [PATCH 2/2] t5556: replace test_i18ngrep with a simple grep Ramsay Jones
2018-02-12 20:18 ` Junio C Hamano
2018-02-12 21:12 ` Junio C Hamano
2018-02-13 1:58 ` Ramsay Jones
2018-02-13 7:51 ` Junio C Hamano
2018-02-13 10:04 ` SZEDER Gábor
2018-02-13 17:08 ` Junio C Hamano
2018-02-13 17:26 ` Jeff King
2018-02-13 18:10 ` Junio C Hamano
2018-02-27 20:16 ` Junio C Hamano
2018-02-27 22:05 ` Junio C Hamano
2018-02-27 23:47 ` Ramsay Jones
2018-02-28 0:42 ` SZEDER Gábor
2018-02-28 15:33 ` Ramsay Jones [this message]
2018-02-28 16:18 ` 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
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=ffc3d3dc-6d21-4273-5362-cbf32e7e4e59@ramsayjones.plus.com \
--to=ramsay@ramsayjones.plus.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=szeder.dev@gmail.com \
/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).