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

Re: [PATCH 2/2] git-svn: support fetch with autocrlf on

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 13, 2010, 23:59 UTC
Message-ID
<alpine.DEB.1.00.1002140055550.20986@pacific.mpi-cbg.de>
In-Reply-To
<40aa078e1002130616u478397c0xf757d5424630e6cf@mail.gmail.com>
Hi,
On Sat, 13 Feb 2010, Erik Faye-Lund wrote:
Show 5 quoted lines
> I don't think it affects svn dcommit in any way, except from the 
> implicit svn rebase that svn dcommit performs. d3c9634e sets 
> core.autocrlf to "false" on init, but re-enabling it hasn't shown any 
> problems in my end. I'm using git-svn with these patches and 
> core.autocrlf enabled every day at my day-job.

To elicit a warm and fuzzy feeling about your patch, you will have to analyze the code paaths of dcommit, and how crlf affects them. Then you will have to describe why dcommit does not have a problem with crlf with your patches anymore.

Remember, the idea of a commit message is to optimize the overall time balance, i.e. avoid the many to perform what the one can do for them. And since you have to do that analysis for yourself anyway, it makes sense to write up the result in the commit message.

Thanks, Dscho

Previous: Erik Faye-LundNext: Erik Faye-Lund
Message 5 of 11 in “hash-object: support --stdin-paths with --no-filters”
  1. 1/2 hash-object: support --stdin-paths with --no-filtersErik Faye-Lund, Feb 12, 2010
  2. 2/2 git-svn: support fetch with autocrlf onErik Faye-Lund, Feb 12, 2010
  3. Eric WongFeb 13, 2010
  4. Erik Faye-LundFeb 13, 2010
  5. Johannes SchindelinFeb 13, 2010
  6. Erik Faye-LundFeb 14, 2010
  7. Johannes SchindelinFeb 14, 2010
  8. Erik Faye-LundFeb 14, 2010
  9. Johannes SchindelinFeb 13, 2010
  10. Dmitry PotapovFeb 12, 2010
  11. Erik Faye-LundFeb 14, 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.