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

Re: [PATCH] Documentation: add a planning document for the next CLI revamp

From
Julian Phillips <julian@quantumfyre.co.uk>
Date
Oct 30, 2008, 15:25 UTC
Message-ID
<alpine.LNX.2.00.0810301518300.13964@reaper.quantumfyre.co.uk>
In-Reply-To
<20081030132453.GB24098@artemis.corp>
On Thu, 30 Oct 2008, Pierre Habouzit wrote:
Show 25 quoted lines
> On Thu, Oct 30, 2008 at 03:48:05AM +0000, Sam Vilain wrote:
>> +Working with patches
>> +--------------------
>> +
>> +  * 'git send-email' should prompt for all SMTP-related information
>> +    about sending e-mail when it is running with no configuration.
>> +    Because these days /usr/lib/sendmail is rarely configured
>> +    correctly.
>
> And when the user answer them, it should set them (a bit like zsh does
> when it's run from the first time e.g.)
>
>> +
>> +  * other git send-email functionality which has bitten people -
>> +    particularly building the recipient list - should prompt for
>> +    confirmation until configured to be automatic.
>> +
>
>  * git-send-email should be either more interactive, or less: either
>    just use the damn configuration, or propose a mode where it spawns
>    an editor for each patch so that you can add further comments.
>
>  * git-send-email should be able to format-patches by himself (IOW
>    accept most of format-patch arguments and deal with the patch list
>    by himself, which is usable if the previous point is implemented).
This gets my vote ...

These are two of the reasons that I ended up ignoring git-send-email and writing my own replacement. I found the whole format-patch/send-email dance too cumbersome and confusing - particularly for sending a single patch. To send a single patch I ended up with the command:

git mail-commmits --edit HEAD~1
It would be nice if I could replace this with:
git send-email --edit HEAD~1
;)
Show 5 quoted lines
>
>> +  * 'git am -3' the default; with global option to make it not the
>> +    default for those that prefer the speed of -2
>> +
>> +
-- 
Julian

  ---
Blessed be those who initiate lively discussions with the hopelessly mute,
for they shall be know as Dentists.
Previous: Pierre HabouzitNext: Jeff King
Message 5 of 49 in “Documentation: add a planning document for the next CLI revamp”
  1. Documentation: add a planning document for the next CLI revampSam Vilain, Oct 30, 2008
  2. Stefan KarpinskiOct 30, 2008
  3. Kyle MoffettOct 31, 2008
  4. Pierre HabouzitOct 30, 2008
  5. Julian PhillipsOct 30, 2008
  6. Jeff KingOct 31, 2008
  7. Junio C HamanoNov 2, 2008
  8. Pierre HabouzitNov 3, 2008
  9. Nicolas PitreOct 30, 2008
  10. Shawn O. PearceOct 30, 2008
  11. Mike HommeyOct 30, 2008
  12. Pierre HabouzitOct 30, 2008
  13. Nicolas PitreOct 30, 2008
  14. Sam VilainOct 30, 2008
  15. Nicolas PitreOct 30, 2008
  16. Yann DirsonOct 30, 2008
  17. Sam VilainOct 30, 2008
  18. Jakub NarebskiOct 30, 2008
  19. Sam VilainOct 31, 2008
  20. Jakub NarebskiOct 31, 2008
  21. Sam VilainNov 3, 2008
  22. Jakub NarebskiNov 3, 2008
  23. Johannes SchindelinNov 1, 2008
  24. Theodore TsoOct 30, 2008
  25. Pierre HabouzitOct 30, 2008
  26. Theodore TsoOct 30, 2008
  27. Pierre HabouzitOct 30, 2008
  28. Sam VilainOct 30, 2008
  29. Nicolas PitreOct 30, 2008
  30. Junio C HamanoNov 2, 2008
  31. Theodore TsoNov 2, 2008
  32. Andreas EricssonOct 30, 2008
  33. Elijah NewrenNov 1, 2008
  34. Matthieu MoyOct 30, 2008
  35. Nicolas PitreOct 30, 2008
  36. Pierre HabouzitOct 30, 2008
  37. Nicolas PitreOct 30, 2008
  38. Sam VilainOct 30, 2008
  39. Junio C HamanoNov 2, 2008
  40. Sam VilainNov 3, 2008
  41. Elijah NewrenNov 1, 2008
  42. Sam VilainOct 30, 2008
  43. Theodore TsoOct 30, 2008
  44. Elijah NewrenNov 1, 2008
  45. Theodore TsoNov 2, 2008
  46. Elijah NewrenNov 2, 2008
  47. Elijah NewrenNov 1, 2008
  48. Junio C HamanoNov 2, 2008
  49. Elijah NewrenNov 1, 2008

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.