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

Re: [PATCH] doc/git-send-email: mention sendemail.cc config variable

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 30, 2008, 08:00 UTC
Message-ID
<7vocyu3xei.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<200812291429.01822.markus.heidelberg@web.de>
Markus Heidelberg <markus.heidelberg@web.de> writes:
> It is already in next, I think a following patch should be against next
> now, shouldn't it?
Surely, and thanks.
If you look at the output of
	$ git log --first-parent origin/master..origin/next

You will find the tip of mh/maint-sendmail-cc-doc topic branch is at bd7c6e7 (doc/git-send-email: mention sendemail.cc config variable, 2008-12-29). I'll apply any follow-up patch to the topic on top of that commit, and then merge the result to 'next' (and 'master'/'maint' when the result is ready).

In rare cases when there are other topics in 'next' that touch vicinity of the code you are modifying, a patch made against 'next' may not apply cleanly to the topic, but I'll wiggle it to apply anyway (that is what the maintainers do), so it would certainly be nicer if you sent a patch to the tip of the topic you are updating, but there is no need to worry about such conflicts too much.

Previous: Markus HeidelbergNext: Markus Heidelberg
Message 4 of 6 in “doc/git-send-email: mention sendemail.cc config variable”
  1. doc/git-send-email: mention sendemail.cc config variableMarkus Heidelberg, Dec 28, 2008
  2. Thomas RastDec 29, 2008
  3. Markus HeidelbergDec 29, 2008
  4. Junio C HamanoDec 30, 2008
  5. Markus HeidelbergJan 1, 2009
  6. Thomas RastJan 2, 2009

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.