Re: git-email automatic --to detection?

From: Matthieu Moy <matthieu.moy@imag.fr>
Date: Feb 25, 2008, 18:57 UTC
Message-ID: <vpqoda43lva.fsf@bauges.imag.fr>
In-Reply-To: <20080225183413.GA15131@sigill.intra.peff.net>

Jeff King <peff@peff.net> writes:

>   - there's more than _one_ maintainer for the repo; in fact, who you
>     email depends on what part of the code you are touching

Yes, but a sane default address to send to can be given by the repository you make your original clone from.

The really nice thing with the way darcs does it is that it makes it extremely easy for an occasional contribution. If the maintainer configured his stuff correctly, it's really "darcs get; ... ; darcs record; darcs send". git-send-email is nice, but harder to use for a first-timer.

>   - 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)

True, but for the case of multiple maintainers, that would break merging between maintainers on that particular part.

You can have a maintainer A advertizing for A@domain.com, and a "sub-maintainer" B advertizing for B@domain.com. If A merges from B, he doesn't want his advertized adress to become the one of B.

>   - this information can potentially be inferred from git shortlog
>     and/or blame; this addresses the problem of data becoming stale

Yes and no. git@vger.kernel.org won't appear anywhere in these for example.

-- 
Matthieu