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

Re: [PATCH 3/4] git-am: Add command line parameter `--keep-cr` passing it to git-mailsplit.

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 12, 2010, 21:54 UTC
Message-ID
<7vmxzenmrb.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20100212210546.GC32018@pille.home>
"Stefan-W. Hahn" <stefan.hahn@s-hahn.de> writes:
Show 14 quoted lines
> Also sprach Junio C Hamano am Thu, 11 Feb 2010 at 15:21:32 -0800:
>> "Stefan-W. Hahn" <stefan.hahn@s-hahn.de> writes:
>> 
>> > If applying patches with the following command sequence
>> >
>> >    git format-patch --stdout ... | git am ...
>> >
>> > in repositories having files with dos and unix line endings
>> > git-mailsplit, which is called from git-am must be called with
>> > `--keep-cr` parameter since commit c2ca1d79.
>> 
>> Sorry, I cannot parse this.
>
> What?
What I said.  I wasn't able to parse it.  If it were:
    If applying patches with the following command sequence
       git format-patch --stdout ... | git am ...
    in repositories having files with dos and unix line endings,
    git-mailsplit, which is called from git-am, must be called with
    `--keep-cr` parameter since commit c2ca1d79.

iow, two additional commas, I would have been able to, but I was not certain that is what you meant.

Show 6 quoted lines
>> > +e,keep-cr       pass --keep-cr flag to git-mailsplit for mbox format
>> 
>> This short form -e does not make much sense to me.  Why is it -e, and do
>> we even need a short form in the first place?
>
> Just for shortening the commandline.

That much I know already ;-) and you probably know that I knew when I wrote this, which you somehow omitted from your quote:

    ... We may want to use short-and-sweet 'e' for something more
    important and common, and we would regret for letting this option
    squat on it later.

The shorter one can come later after people find --keep-cr is something they often need to use and deserve a shorter form, but not until then.

Previous: Stefan-W. HahnNext: Stefan-W. Hahn
Message 12 of 13 in “[PATCHv2 0/4] Using git-mailsplit in mixed line ending environment”
  1. Stefan-W. HahnFeb 11, 2010
  2. 1/4 git-mailsplit: Show parameter '--keep-cr' in usage and documentationStefan-W. Hahn, Feb 11, 2010
  3. 2/4 git-mailsplit: add `mailsplit.keepcr` configuration variable.Stefan-W. Hahn, Feb 11, 2010
  4. Junio C HamanoFeb 11, 2010
  5. Stefan-W. HahnFeb 12, 2010
  6. Junio C HamanoFeb 12, 2010
  7. Junio C HamanoFeb 12, 2010
  8. Stefan-W. HahnFeb 12, 2010
  9. 3/4 git-am: Add command line parameter `--keep-cr` passing it to git-mailsplit.Stefan-W. Hahn, Feb 11, 2010
  10. Junio C HamanoFeb 11, 2010
  11. Stefan-W. HahnFeb 12, 2010
  12. Junio C HamanoFeb 12, 2010
  13. 4/4 Adding test for `--keep-cr` for git-mailsplit and git-am.Stefan-W. Hahn, Feb 11, 2010

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.