From: Junio C Hamano <gitster@pobox.com>
To: Stephen & Linda Smith <ischis2@cox.net>
Cc: git@vger.kernel.org, Will Palmer <wmpalmer@gmail.com>,
Alexander Kuleshov <kuleshovmail@gmail.com>,
Eric Sunshine <sunshine@sunshineco.com>
Subject: Re: What's cooking in git.git (Jan 2016, #01; Mon, 4)
Date: Mon, 04 Jan 2016 19:36:05 -0800 [thread overview]
Message-ID: <xmqqy4c4k89m.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1718717.tR0GOgDc0N@thunderbird> (Stephen & Linda Smith's message of "Mon, 04 Jan 2016 19:44:19 -0700")
Stephen & Linda Smith <ischis2@cox.net> writes:
> On Monday, January 04, 2016 03:44:33 PM Junio C Hamano wrote:
>> Becoming tired of waiting for a reroll.
>> ($gmane/271213).
>> Anybody wants to help rerolling this? Otherwise will discard.
>
> <snip>
>
>> Becoming tired of waiting for a reroll.
>> Anybody wants to help rerolling this? Otherwise will discard.
> > ($gmane/272180).
>
> What do you mean by rerolling this? If you mean that you would
> like someone to pick up the patch and try and get it though then I
> don't mind helping.
More or less. I do not mind if these topics disappeared, either,
but we have spent review and discussion bandwidth for these
unfinished topics and we may want to take them to the completion.
> For my education, how does this affect the sign-off proceedure?
Depending on the extent of changes from the original version, either
you take the authorship (with comment in the log message saying that
it is based on Such and Such's patches) or you still keep them as
the author (with comment in the log message saying that you extended
it in such and such way). In either case, as long as their original
remains in the resulting patch, you retain their Sign-off and then
add your Sign-off at the end.
If you take the ideas from their series and rewrite everything from
scratch, you would take the authorship, with comment in the log
message saying that you took inspiration from Such and Such's
patches, and have only your Sign-off.
next prev parent reply other threads:[~2016-01-05 3:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 2:44 What's cooking in git.git (Jan 2016, #01; Mon, 4) Stephen & Linda Smith
2016-01-05 3:36 ` Junio C Hamano [this message]
2016-01-05 4:32 ` Stephen & Linda Smith
2016-01-07 3:56 ` Picking up old threads/patches Stephen & Linda Smith
2016-01-07 3:59 ` Stephen & Linda Smith
2016-01-07 8:03 ` Jeff King
2016-01-07 13:29 ` Stephen & Linda Smith
-- strict thread matches above, loose matches on Subject: below --
2016-01-04 23:44 What's cooking in git.git (Jan 2016, #01; Mon, 4) 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=xmqqy4c4k89m.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ischis2@cox.net \
--cc=kuleshovmail@gmail.com \
--cc=sunshine@sunshineco.com \
--cc=wmpalmer@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.
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.