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, 18:44 UTC
Message-ID
<7vhaizu3j5.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20130421105612.GA28959@elie.Belkin>
Jonathan Nieder <jrnieder@gmail.com> writes:
> My personal preference is that patches come on the git list, are
> reviewed here, and then go to your fork of the Git project that Junio
> can periodically pull from at your request (like git-svn).  But of
> course this is up to you, too.
And also me ;-)
Yes, I very much prefer the way how git-svn is managed.
Previous: Jonathan NiederNext: Michael Haggerty
Message 3 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.