From: Lars Noschinski <lars@public.noschinski.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Fabian Emmes <fabian.emmes@rwth-aachen.de>, git@vger.kernel.org
Subject: Re: [PATCH] cvsserver: add option to configure commit message
Date: Sun, 4 Jan 2009 12:23:18 +0100 [thread overview]
Message-ID: <20090104112318.GB7732@lars.home.noschinski.de> (raw)
In-Reply-To: <7viqovz8y0.fsf@gitster.siamese.dyndns.org>
* Junio C Hamano <gitster@pobox.com> [09-01-04 12:13]:
>Fabian Emmes <fabian.emmes@rwth-aachen.de> writes:
>
>> cvsserver annotates each commit message by "via git-CVS emulator". This is
>> made configurable via gitcvs.commitmsgannotation.
>>
>> Signed-off-by: Fabian Emmes <fabian.emmes@rwth-aachen.de>
>> Signed-off-by: Lars Noschinski <lars@public.noschinski.de>
>
>I do not see the development history behind this and am somewhat puzzled
>by these two S-o-b lines. Is it "Fabian developed it, showed it to Lars
>who cleaned it up and/or enhanced it and here is the result"? Or is it
>"Lars developed it, circulated it in his closer circle, Fabian found it
>useful and worthy for inclusion and sending it to the mailing list"?
It is "Fabian and Lars developed it and Fabian is the one who mailed it
for inclusion". We could just leave off the second S-o-b line, if this
is less irritating?
>Whichever it is, I just will take it as "This is co-developed and between
>the authors Fabian is the primary author" and apply.
Fine with me.
- Lars.
next prev parent reply other threads:[~2009-01-04 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 15:40 [PATCH] cvsserver: add option to configure commit message Fabian Emmes
2009-01-02 15:40 ` [PATCH] cvsserver: change generation of CVS author names Fabian Emmes
2009-01-03 22:14 ` Junio C Hamano
2009-01-04 11:13 ` Lars Noschinski
2009-01-06 8:18 ` Junio C Hamano
2009-01-04 10:01 ` [PATCH] cvsserver: add option to configure commit message Junio C Hamano
2009-01-04 11:23 ` Lars Noschinski [this message]
2009-01-04 19:20 ` 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=20090104112318.GB7732@lars.home.noschinski.de \
--to=lars@public.noschinski.de \
--cc=fabian.emmes@rwth-aachen.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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 NNTP newsgroup(s).