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

Re: [PATCH 2/2] Improve doc for format-patch threading options.

From
Markus Heidelberg <markus.heidelberg@web.de>
Date
Jul 23, 2009, 05:31 UTC
Message-ID
<200907230731.14430.markus.heidelberg@web.de>
In-Reply-To
<1248298771-21075-3-git-send-email-ydirson@altern.org>
Yann Dirson, 22.07.2009:
> This hopefully makes the relationship between threading options of
> format-patch and send-email easier to grasp.
Yes, it does.
Show 47 quoted lines
> Signed-off-by: Yann Dirson <ydirson@altern.org>
> ---
>  Documentation/git-format-patch.txt |   22 +++++++++++++++-------
>  Documentation/git-send-email.txt   |   21 ++++++++++++++++-----
>  2 files changed, 31 insertions(+), 12 deletions(-)
> 
> diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt
> index 6f1fc80..687e667 100644
> --- a/Documentation/git-format-patch.txt
> +++ b/Documentation/git-format-patch.txt
> @@ -10,7 +10,7 @@ SYNOPSIS
>  --------
>  [verse]
>  'git format-patch' [-k] [(-o|--output-directory) <dir> | --stdout]
> -		   [--thread[=<style>]]
> +		   [--no-thread | --thread[=<style>]]
>  		   [(--attach|--inline)[=<boundary>] | --no-attach]
>  		   [-s | --signoff]
>  		   [-n | --numbered | -N | --no-numbered]
> @@ -124,17 +124,25 @@ include::diff-options.txt[]
>  	second part, with "Content-Disposition: inline".
>  
>  --thread[=<style>]::
> -	Add In-Reply-To and References headers to make the second and
> -	subsequent mails appear as replies to the first.  Also generates
> -	the Message-Id header to reference.
> +--no-thread::
> +	Controls addition of In-Reply-To and References headers to
> +	make the second and subsequent mails appear as replies to the
> +	first.  Also controls generation of the Message-Id header to
> +	reference.
>  +
>  The optional <style> argument can be either `shallow` or `deep`.
>  'shallow' threading makes every mail a reply to the head of the
>  series, where the head is chosen from the cover letter, the
>  `\--in-reply-to`, and the first patch mail, in this order.  'deep'
> -threading makes every mail a reply to the previous one.  If not
> -specified, defaults to the 'format.thread' configuration, or `shallow`
> -if that is not set.
> +threading makes every mail a reply to the previous one.
> ++
> +The default is --no-thread, unless the 'format.thread' configuration
> +is set.  If --thread is specified without a style, it defaults to the
> +style specified by 'format.thread' if any, or else `shallow`.
> ++
> +Beware that the default for 'git send-email' is to thread emails
> +itself.  If you want 'git format-patch' to take care of hreading, you
                                                           ^^^^^^^^
threading
I guess Junio can squash this in.
> +will want to ensure that threading is disabled for 'git send-email'.
>  
>  --in-reply-to=Message-Id::
>  	Make the first mail (or all the mails with --no-thread) appear as a
Previous: Yann DirsonNext: Junio C Hamano
Message 16 of 17 in “format-patch / send-mail thrading documentation”
  1. 0/2 format-patch / send-mail thrading documentationYann Dirson, Jul 5, 2009
  2. 1/2 List send-email config options in config.txt.Yann Dirson, Jul 5, 2009
  3. 2/2 Improve doc for format-patch threading options.Yann Dirson, Jul 5, 2009
  4. Markus HeidelbergJul 6, 2009
  5. Markus HeidelbergJul 6, 2009
  6. Yann DirsonJul 16, 2009
  7. Markus HeidelbergJul 16, 2009
  8. Yann DirsonJul 17, 2009
  9. Markus HeidelbergJul 17, 2009
  10. Yann DirsonJul 22, 2009
  11. Junio C HamanoJul 6, 2009
  12. Yann DirsonJul 16, 2009
  13. 0/2 format-patch / send-mail threading documentationYann Dirson, Jul 22, 2009
  14. 1/2 List send-email config options in config.txt.Yann Dirson, Jul 22, 2009
  15. 2/2 Improve doc for format-patch threading options.Yann Dirson, Jul 22, 2009
  16. Markus HeidelbergJul 23, 2009
  17. Junio C HamanoJul 22, 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.