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

Re: [PATCH v2 4/6] add a test for git-send-email for non-threaded mails

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 8, 2009, 07:00 UTC
Message-ID
<7vd49f8b1f.fsf@alter.siamese.dyndns.org>
In-Reply-To
<200906080842.00357.markus.heidelberg@web.de>
Markus Heidelberg <markus.heidelberg@web.de> writes:
Show 8 quoted lines
> Signed-off-by: Markus Heidelberg <markus.heidelberg@web.de>
> ---
>
> Differences to v1:
> * dump stdout into a file and grep this
> * use "test_must_fail grep" instead of "!git send-email"
>   I'm not sure about this. When should test_must_fail be used and when
>   is !command OK?
Thanks.

Generally, we protect "git" (i.e. what we write ourselves) with test_must_fail so that we can catch stupid segfaulting crash we introduce ourselves (unlike "! git foo", "test_must_fail git foo" says "oh, no, it did not correctly fail" if git segfaults). We do not expect "grep" to segfault (iow we are not testing "grep"), so it is customary to say "! grep".

Previous: Markus HeidelbergNext: Markus Heidelberg
Message 34 of 38 in “fixes for git-send-email”
  1. 0/6 fixes for git-send-emailMarkus Heidelberg, Jun 7, 2009
  2. 1/6 send-email: fix a typo in a commentMarkus Heidelberg, Jun 7, 2009
  3. Junio C HamanoJun 8, 2009
  4. Markus HeidelbergJun 9, 2009
  5. 1/2 add a test for git-send-email for non-threaded mailsMarkus Heidelberg, Jun 9, 2009
  6. 2/2 send-email: fix non-threaded mailsMarkus Heidelberg, Jun 9, 2009
  7. 2/6 add a test for git-send-email for threaded mails without chain-reply-toMarkus Heidelberg, Jun 7, 2009
  8. Junio C HamanoJun 7, 2009
  9. Markus HeidelbergJun 8, 2009
  10. 2/6 add a test for git-send-email for threaded mails without chain-reply-toMarkus Heidelberg, Jun 8, 2009
  11. Junio C HamanoJun 8, 2009
  12. 3/6 send-email: fix threaded mails without chain-reply-toMarkus Heidelberg, Jun 7, 2009
  13. Junio C HamanoJun 10, 2009
  14. [RF sanity check] send-email threading fixes (was Re: [PATCH 3/6] send-email: fix threaded mails without chain-reply-to)Junio C Hamano, Jun 10, 2009
  15. Markus HeidelbergJun 11, 2009
  16. Junio C HamanoJun 11, 2009
  17. Markus HeidelbergJun 11, 2009
  18. Junio C HamanoJun 11, 2009
  19. 0/6 send-email threading fixesMarkus Heidelberg, Jun 12, 2009
  20. 1/6 add a test for git-send-email for non-threaded mailsMarkus Heidelberg, Jun 12, 2009
  21. 2/6 send-email: fix non-threaded mailsMarkus Heidelberg, Jun 12, 2009
  22. 3/6 doc/send-email: clarify the behavior of --in-reply-to with --no-threadMarkus Heidelberg, Jun 12, 2009
  23. 4/6 add a test for git-send-email for threaded mails without chain-reply-toMarkus Heidelberg, Jun 12, 2009
  24. 5/6 send-email: fix threaded mails without chain-reply-toMarkus Heidelberg, Jun 12, 2009
  25. 6/6 send-email: fix a typo in a commentMarkus Heidelberg, Jun 12, 2009
  26. 1/6 add a test for git-send-email for non-threaded mailsJunio C Hamano, Jun 10, 2009
  27. 2/6 send-email: fix non-threaded mailsJunio C Hamano, Jun 10, 2009
  28. 3/6 doc/send-email: clarify the behavior of --in-reply-to with --no-threadJunio C Hamano, Jun 10, 2009
  29. 4/6 send-email: fix threaded mails without chain-reply-toJunio C Hamano, Jun 10, 2009
  30. 5/6 add a test for git-send-email for threaded mails without chain-reply-toJunio C Hamano, Jun 10, 2009
  31. 6/6 send-email: fix a typo in a commentJunio C Hamano, Jun 10, 2009
  32. 4/6 add a test for git-send-email for non-threaded mailsMarkus Heidelberg, Jun 7, 2009
  33. Markus HeidelbergJun 8, 2009
  34. Junio C HamanoJun 8, 2009
  35. 4/6 add a test for git-send-email for non-threaded mailsMarkus Heidelberg, Jun 8, 2009
  36. 5/6 send-email: fix non-threaded mailsMarkus Heidelberg, Jun 7, 2009
  37. 5/6 send-email: fix non-threaded mailsMarkus Heidelberg, Jun 8, 2009
  38. 6/6 doc/send-email: clarify the behavior of --in-reply-to with --no-threadMarkus Heidelberg, Jun 7, 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.