git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: John Goerzen <jgoerzen@complete.org>, git@vger.kernel.org
Subject: Re: git-email automatic --to detection?
Date: Mon, 25 Feb 2008 11:47:07 -0800	[thread overview]
Message-ID: <7vabloizt0.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080225183413.GA15131@sigill.intra.peff.net> (Jeff King's message of "Mon, 25 Feb 2008 13:34:14 -0500")

Jeff King <peff@peff.net> writes:

> There was some discussion about this a while back for the kernel. Some
> relevant points that I recall:
>
>   - there's more than _one_ maintainer for the repo; in fact, who you
>     email depends on what part of the code you are touching
>
>   - this information could be shipped as part of the repo (i.e., under
>     version control like the rest of the project, as it changes with the
>     project)
>
>   - this information can potentially be inferred from git shortlog
>     and/or blame; this addresses the problem of data becoming stale
>
> See this thread:
>
>   http://mid.gmane.org/1187110824.32555.76.camel@localhost

That matches my recollection, but I think the most important
point to take home from these points are that you cannot blindly
say that the tool can figure it out and do that for you.  We
could probably have an automated way to scan shortlog and
whatnot and offer suggestions, but the final determination of
the recipient addresses needs to be done by the end user.

Which in short means README or Documentation/SubmittingPatches
would be the most appropriate place for that information.

      parent reply	other threads:[~2008-02-25 19:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-24 22:29 git-email automatic --to detection? John Goerzen
2008-02-24 22:56 ` Paolo Ciarrocchi
2008-02-25 15:07   ` John Goerzen
2008-02-25 18:35   ` Jeff King
2008-02-25 18:56     ` Paolo Ciarrocchi
2008-02-25 14:39 ` Miklos Vajna
2008-02-25 15:08   ` John Goerzen
2008-02-25 20:50     ` Miklos Vajna
2008-02-25 18:34 ` Jeff King
2008-02-25 18:57   ` Matthieu Moy
2008-02-25 19:19     ` Jeff King
2008-02-25 20:02     ` John Goerzen
2008-02-26  9:23       ` Matthieu Moy
2008-02-26 14:07         ` John Goerzen
2008-02-25 20:55     ` Miklos Vajna
2008-02-26 13:59       ` John Goerzen
2008-02-26 17:44         ` Miklos Vajna
2008-02-25 19:47   ` Junio C Hamano [this message]

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=7vabloizt0.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jgoerzen@complete.org \
    --cc=peff@peff.net \
    /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).