git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH v3 0/1] git-multimail: a replacement for post-receive-email

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 21, 2013, 22:12 UTC
Message-ID
<7va9orsfd7.fsf@alter.siamese.dyndns.org>
In-Reply-To
<517445E5.3080304@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
> That seems very workable.
That is pretty much it.
> What is your preference regarding the history to date?

The only thing I deeply care about is that initial and subsequent "git pull" I'll do from you [*1*] will pull in commits that touch only the "multimail" part in the contrib/ area and not mixed with unrelated changes to other areas.

If the history you have so far would later help others learn the motivation, design, constraints etc. while developing it, which cannot be easily read from the resulting code, i.e. help maintaining it in general, it's a good idea to keep it. In such a case, however, people may want to review that history as well.

If it is the "oops, it didn't work, let's try another" kind of "record as we build" type of history that may not help the future maintainace that much, you may instead want to start with a single code-dump "here is the first public version" (which is reviewed in this thread, I think) without the history behind it.

Your choice, in other words ;-)
[Footnote]

*1* This does not even have to be a stable URL I would place in remote.multimail.url configuration; it does not even have to be a non-rewinding tree.

Previous: Michael HaggertyNext: Junio C Hamano
Message 5 of 7 in “git-multimail: a replacement for post-receive-email”
  1. 0/1 git-multimail: a replacement for post-receive-emailMichael Haggerty, Apr 21, 2013
  2. Jonathan NiederApr 21, 2013
  3. Junio C HamanoApr 21, 2013
  4. Michael HaggertyApr 21, 2013
  5. Junio C HamanoApr 21, 2013
  6. Junio C HamanoApr 21, 2013
  7. Jonathan NiederApr 21, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.