From: David Kastrup <dak@gnu.org>
To: Christian Couder <christian.couder@gmail.com>
Cc: "Randall S. Becker" <rsbecker@nexbridge.com>,
Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
git <git@vger.kernel.org>, Jeff King <peff@peff.net>,
Scott Chacon <schacon@gmail.com>
Subject: Re: Promoting Git developers
Date: Mon, 16 Mar 2015 10:20:34 +0100 [thread overview]
Message-ID: <87a8zdguxp.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <CAP8UFD08xoJ2H8XgfDbPfHddX9YFpFgbrY+PZ5Tphuot7JwGvw@mail.gmail.com> (Christian Couder's message of "Mon, 16 Mar 2015 10:10:28 +0100")
Christian Couder <christian.couder@gmail.com> writes:
> On Sun, Mar 15, 2015 at 11:43 PM, Randall S. Becker
> <rsbecker@nexbridge.com> wrote:
>>> On March 15, 2015 6:19 PM Christian Couder wrote:
>> <snip>
>>> Just one suggestion on the name and half a comment.
>>>
>>> How would "Git Review" (or "Git Monthly Review", or replace your favourite
>>> "how-often-per-period-ly" in its name) sound? I meant it to sound similar
>> to
>>> academic journals that summarize and review contemporary works in the
>> field
>>> and keeps your original "pun" about our culture around "patch reviews".
>
> I would be ok for that but there is already this Gerrit related command:
>
> http://www.mediawiki.org/wiki/Gerrit/git-review
>
> Maybe I can just use "Git Rev", but it doesn't tell that it is about news?
>
>> If I may humbly offer the suggestion that "Git Blame" would be a far more
>> appropriate pun as a name :)
>
> You don't want me to steal Junio's blog title:
>
> http://git-blame.blogspot.fr/
>
> don't you?
"Git Annotate"?
--
David Kastrup
next prev parent reply other threads:[~2015-03-16 9:20 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8zdguxp.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=christian.couder@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.com \
--cc=schacon@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.