From: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
To: Carlos O'Donell <carlos@redhat.com>, Florian Weimer <fweimer@redhat.com>
Cc: nd <nd@arm.com>, Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>,
Rafal Luzynski <digitalfreak@lingonborough.com>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: 2.29 freeze update: Last fortnight
Date: Tue, 22 Jan 2019 13:11:03 +0000 [thread overview]
Message-ID: <4a3e6199-b4a8-331d-895a-9a30f2df4873@arm.com> (raw)
In-Reply-To: <7d57b1ea-da5a-3039-ddcd-e4acde8ed464@redhat.com>
On 22/01/2019 13:06, Carlos O'Donell wrote:
> On 1/22/19 7:00 AM, Florian Weimer wrote:
>> * Carlos O'Donell:
>>
>>> I expect to commit the fix as soon as Torvald and Rik let me use
>>> their Signed-off-by.
>>
>> “Signed-off-by” probably isn't the right term to use in this context.
>> What exactly do you mean?
>
> Both Torvald nad Rik worked on the patch with me.
>
> I can't use their 'Signed-off-by' without them authorizing
> it based on the final version.
>
> So I am asking them for it so I can record their work on the patch
> with me.
>
> What else would I use?
this was mentioned earlier in the ChangeLog discussion:
https://git.savannah.gnu.org/cgit/gnulib.git/tree/build-aux/gitlog-to-changelog
(see SPECIAL SYNTAX part: it uses Co-authored-by:)
next prev parent reply other threads:[~2019-01-22 13:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 14:37 2.29 freeze update: Last fortnight Siddhesh Poyarekar
2019-01-15 16:52 ` Rafal Luzynski
2019-01-15 17:02 ` Zack Weinberg
2019-01-15 17:16 ` Rafal Luzynski
2019-01-15 17:49 ` Paul Eggert
2019-01-15 18:16 ` Rafal Luzynski
2019-01-15 18:22 ` Paul Eggert
2019-01-15 22:03 ` Rafal Luzynski
2019-01-15 17:09 ` Carlos O'Donell
2019-01-17 6:30 ` TAMUKI Shoichi
2019-01-17 6:29 ` TAMUKI Shoichi
2019-01-17 20:32 ` Rafal Luzynski
2019-01-18 13:58 ` TAMUKI Shoichi
2019-01-18 15:35 ` Rafal Luzynski
2019-01-15 20:09 ` Jochen Hein
2019-01-16 3:44 ` Siddhesh Poyarekar
2019-01-15 20:17 ` Carlos O'Donell
2019-01-16 3:47 ` Siddhesh Poyarekar
2019-01-22 3:28 ` Siddhesh Poyarekar
2019-01-22 3:52 ` H.J. Lu
2019-01-22 22:14 ` Joseph Myers
2019-01-22 4:21 ` Carlos O'Donell
2019-01-22 12:00 ` Florian Weimer
2019-01-22 13:06 ` Carlos O'Donell
2019-01-22 13:11 ` Szabolcs Nagy [this message]
2019-01-22 13:23 ` Carlos O'Donell
2019-01-22 15:17 ` Siddhesh Poyarekar
2019-01-22 15:48 ` Carlos O'Donell
2019-01-22 16:06 ` DCO or Copyright Assignment? Why not both Siddhesh Poyarekar
2019-01-28 13:00 ` Florian Weimer
2019-01-22 10:18 ` 2.29 freeze update: Last fortnight Rafal Luzynski
2019-01-16 3:13 ` H.J. Lu
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: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4a3e6199-b4a8-331d-895a-9a30f2df4873@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=siddhesh@gotplt.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.
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).