All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-multimail: update to version 1.0.0
Date: Mon, 07 Apr 2014 11:56:42 -0700	[thread overview]
Message-ID: <xmqqd2gtm0id.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1396884040-26014-1-git-send-email-mhagger@alum.mit.edu> (Michael Haggerty's message of "Mon, 7 Apr 2014 17:20:40 +0200")

Michael Haggerty <mhagger@alum.mit.edu> writes:

> ...
> Contributions-by: Raphaël Hertzog <hertzog@debian.org>
> Contributions-by: Eric Berberich <eric.berberich@gmail.com>
> Contributions-by: Michiel Holtkamp <git@elfstone.nl>
> Contributions-by: Malte Swart <mswart@devtation.de>
> Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
> ---
> Junio, how would you like other people's contributions to be recorded
> within the Git project?  I have listed them above as
> "Contributions-by".  All of these people have signed off on their
> contributions (recorded in my GitHub repo).  So should I also/instead
> add "Signed-off-by" for those people?

Either is fine, as long as somewhere in that directory:

 - we make it clear that the copy we have in contrib/ is merely for
   "batteries included" convenience;

 - we refer to the canonical source that is your repository;

 - we tell readers to go there to get the authoritative and up to
   date copy, as what we have in contrib/ is possibly stale.

In the longer term, I have a feeling that we may be better off to
make the "git core" tree not be the "batteris included" convenience
tree, though.  In the early days, Linus's rationale for including
"gitk" held true: having tools that are not quite core is a good way
to get people (especially those without C background) involved in
the still-small project in its infancy to help nurture the developer
community.  The same reasoning stood behind the merging of "gitweb".

We already are beyond that stage, and good tools like iMerge and
multimail that can stand on its own may be better off flourishing
outside "git core" tree, still within the same developer community.

  reply	other threads:[~2014-04-07 18:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-07 15:20 [PATCH] git-multimail: update to version 1.0.0 Michael Haggerty
2014-04-07 18:56 ` Junio C Hamano [this message]
2014-04-09 16:01   ` Michael Haggerty
2014-04-09 16:35     ` 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=xmqqd2gtm0id.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=mhagger@alum.mit.edu \
    /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.