From: Junio C Hamano <gitster@pobox.com>
To: Fredrik Gustafsson <iveqy@iveqy.com>
Cc: Duy Nguyen <pclouds@gmail.com>,
"Jason St. John" <jstjohn@purdue.edu>,
Christian Couder <christian.couder@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
David Kastrup <dak@gnu.org>, git <git@vger.kernel.org>
Subject: Re: Promoting Git developers
Date: Thu, 12 Mar 2015 11:43:00 -0700 [thread overview]
Message-ID: <xmqqegou2h1n.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20150312074511.GB12418@paksenarrion.iveqy.com> (Fredrik Gustafsson's message of "Thu, 12 Mar 2015 08:45:11 +0100")
Fredrik Gustafsson <iveqy@iveqy.com> writes:
> On Wed, Mar 11, 2015 at 09:53:22PM -0700, Junio C Hamano wrote:
>> I'd first suggest to employ "icase" to unify *-By and *-by. Perhaps
>> we would want a recommended list somewhere in SubmittingPatches to
>> discourage people from getting too creative?
>
> There's already such list in SubmittingPatches, so there's already quite
> a few to choose from:
>
> Also notice that a real name is used in the Signed-off-by: line. Please
> don't hide your real name.
>
> If you like, you can put extra tags at the end:
>
> 1. "Reported-by:" is used to credit someone who found the bug that
> the patch attempts to fix.
> 2. "Acked-by:" says that the person who is more familiar with the
> area the patch attempts to modify liked the patch.
> 3. "Reviewed-by:", unlike the other tags, can only be offered by
> the reviewer and means that she is completely satisfied that the
> patch is ready for application. It is usually offered only after
> a detailed review.
> 4. "Tested-by:" is used to indicate that the person
> applied the patch and found it to have the desired effect.
>
> You can also create your own tag or use one that's in common usage such as
> "Thanks-to:", "Based-on-patch-by:", or "Mentored-by:".
Hmph, the first step might be to drop that last sentence, I guess,
if we consider this a "mess" and if we want to clean it up.
next prev parent reply other threads:[~2015-03-12 18:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-07 7:18 Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-09 13:57 ` Michael J Gruber
2015-03-09 14:31 ` Promoting Git developers David Kastrup
2015-03-09 18:32 ` Philip Oakley
2015-03-10 7:45 ` Junio C Hamano
2015-03-10 11:51 ` Promoting Git developers (was: Bashing freelancers) Christian Couder
2015-03-10 17:23 ` Promoting Git developers Junio C Hamano
2015-03-11 1:04 ` Jason St. John
2015-03-11 2:13 ` Duy Nguyen
2015-03-11 4:16 ` Junio C Hamano
2015-03-12 2:15 ` Duy Nguyen
2015-03-12 4:53 ` Junio C Hamano
2015-03-12 7:45 ` Fredrik Gustafsson
2015-03-12 18:43 ` Junio C Hamano [this message]
2015-03-11 2:36 ` Junio C Hamano
2015-03-11 7:31 ` Jeff King
2015-03-11 7:38 ` Junio C Hamano
2015-03-11 7:54 ` Jeff King
2015-03-11 21:28 ` Junio C Hamano
2015-03-11 23:17 ` Andrew Ardill
2015-03-12 22:31 ` Jeff King
2015-03-12 22:36 ` Junio C Hamano
2015-03-12 22:43 ` Jeff King
2015-03-12 5:05 ` Junio C Hamano
2015-03-12 22:38 ` Jeff King
2015-03-12 22:58 ` Junio C Hamano
2015-03-15 9:12 ` Christian Couder
2015-03-11 13:53 ` Christian Couder
2015-03-11 20:42 ` Junio C Hamano
2015-03-15 8:46 ` Christian Couder
2015-03-15 22:18 ` Junio C Hamano
2015-03-15 22:43 ` Randall S. Becker
2015-03-16 9:10 ` Christian Couder
2015-03-16 9:20 ` David Kastrup
2015-03-16 17:06 ` Stefan Beller
2015-03-17 20:08 ` Christian Couder
2015-03-17 20:16 ` Junio C Hamano
2015-03-16 23:39 ` David Lang
2015-03-17 5:25 ` Junio C Hamano
2015-03-17 5:56 ` David Lang
2015-03-17 20:15 ` Christian Couder
2015-03-17 9:43 ` Thomas Ferris Nicolaisen
2015-03-17 19:51 ` Christian Couder
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=xmqqegou2h1n.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=christian.couder@gmail.com \
--cc=dak@gnu.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=iveqy@iveqy.com \
--cc=jstjohn@purdue.edu \
--cc=pclouds@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).