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

Re: [PATCH] Trim ending whitespaces in exclude file if needed.

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 18, 2010, 21:54 UTC
Message-ID
<7v39s3416u.fsf@alter.siamese.dyndns.org>
In-Reply-To
<AANLkTimrgGYXDtN_ukWuCpjGTibrMNLQvfpq8fe=VxS_@mail.gmail.com>
"Vasyl'" <vvavrychuk@gmail.com> writes:
Show 7 quoted lines
>> It sounds like there's a story behind this one.  Could you tell it?
>> That would help future readers of this code to easily determine
>> why they shouldn't break it.
>>
> I modify either .git/info/exclude or .gitignore by copy-pasting `git
> status`. But unfortunetly this adds spacing to ends of lines and ignoring
> does not work...

That makes it sound as if you would need a patch to fix your editor or whatever you are using for copy/paste, rather than git, no?

I do not personally have need to ignore paths whose names end with whitespaces, and I do not think anybody with such a need is sane, so in that sense your patch would be less harmful than the purist in me finds issues in it ;-)

But it changes the documented behaviour that requires documentation updates, yes?

Previous: Vasyl'
Message 4 of 4 in “Trim ending whitespaces in exclude file if needed.”
  1. Trim ending whitespaces in exclude file if needed.Vasyl', Oct 15, 2010
  2. Jonathan NiederOct 17, 2010
  3. Vasyl'Oct 17, 2010
  4. Junio C HamanoOct 18, 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.