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

Re: Changing the defaults for send-email / suppress-cc ?

From
Nanako Shiraishi <nanako3@lavabit.com>
Date
Mar 1, 2009, 06:30 UTC
Message-ID
<20090301153000.6117@nanako3.lavabit.com>
In-Reply-To
<7vsklycct9.fsf@gitster.siamese.dyndns.org>
Quoting Junio C Hamano <gitster@pobox.com>:
Show 14 quoted lines
> No matter what different default you choose, there will be people who
> complain about it as long as it is not exactly the default they want.
>
> The only thing I could think of offhand that you could do safely to remedy
> the situation is to make the command fail until you explicitly set your
> default via the configuration, but even then, it is not entirely safe.
>
> You will hear from angry people who use their own wrapper script to "git
> send-email" that gives all necessary options from the command line and now
> they are forced to add configuration to their repository, even though the
> config is never used because their script overrides it from the command
> line.
>
> So, I dunno.

Isn't it an option to introduce a new program, say 'git send', that reimplements what 'git send-email' is meant to be used for, but has a better implementation and a better default setting?

You have a precedence of doing so when you introduced 'git am'. You contined to maintain 'git applymbox' to keep old people happy. You taught new people to use 'git am', and waited until old people learn to like the new command with a shorter name and a saner behavior. After a certain period of time, you deprecated and removed the original program.

d1c5f2a42d7b5c0e3d3862212dea1f09809c4963 "Add git-am, applymbox replacement" http://article.gmane.org/gmane.comp.version-control.git/44376 http://article.gmane.org/gmane.comp.version-control.git/47785

I don't know much about the technical details, but I saw there were a few discussion threads about improving 'git send-email'; one of the recent ones was this.

http://article.gmane.org/gmane.comp.version-control.git/109791

I also saw the original author (Greg?) said that one of the input formats 'git send-email' supports is not worth supporting, or sth like that. A reimplemention to introduce 'git send' may be a good time to deprecate and remove that old input format.

Or is the migration plan like the one you used when you migrated 'git applymbox' to 'git am' considered unacceptable by now, because git is a lot more mature than it used to be back then?

-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
Previous: Sverre RabbelierNext: Jay Soffian
Message 6 of 10 in “Changing the defaults for send-email / suppress-cc ?”
  1. Paul GortmakerFeb 28, 2009
  2. Junio C HamanoMar 1, 2009
  3. Paul GortmakerMar 1, 2009
  4. send-email: confirm auto cc before sendingJay Soffian, Mar 1, 2009
  5. Sverre RabbelierMar 1, 2009
  6. Nanako ShiraishiMar 1, 2009
  7. Jay SoffianMar 1, 2009
  8. Jay SoffianMar 1, 2009
  9. Jay SoffianMar 1, 2009
  10. Teemu LikonenMar 1, 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.