Re: Store autocrlf during init-db (was [msysGit] autocrlf problems with Git-preview20080301.exe)
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 23, 2008, 11:01 UTC
- Message-ID
- <alpine.LSU.1.00.0803231200010.4353@racer.site>
- In-Reply-To
- <alpine.OSX.1.00.0803230943500.7541@cougar>
Hi,
On Sun, 23 Mar 2008, Steffen Prohaska wrote:
Show 35 quoted lines
> On Sun, 23 Mar 2008, Johannes Schindelin wrote: > > > On Sat, 22 Mar 2008, Junio C Hamano wrote: > > > > > > > > Steffen Prohaska <prohaska@zib.de> writes: > > > > > > >> I suppose autocrlf enabled by default could be useful for new > > > >> repositories, but not for working with existing repositories. > > > > > > > > We changed the global default to a sane setting for cross-platform > > > > projects to avoid such problems in the future. This means that > > > > from now on git will take care that any repository newly created > > > > will have sane line endings (LF in the repository; and CRLF in the > > > > work tree if checked out on Windows respectively LF if checked out > > > > on Unix). > > > > > > I've always wondered why you guys used /etc/gitconfig instead of > > > setting it in the templates (or a patch to git-init). > > > > > > I was against the idea of /etc/gitconfig from the very beginning > > > (even before msysgit existed) in git.git itself, but this is a very > > > good example why /etc/gitconfig is a bad idea. It affects > > > _existing_ setups. > > > > > > How about fixing msys port so that it sets the configuration when > > > the user initializes a _new_ repository, without breaking > > > repositories the user has been happily using? > > > > Makes sense. > > Hmm. I am not convinced. > > Setting autocrlf for every repository limits the user's options to > override the default.
Then maybe a way for the user to override the global templates is what we need? I can see that this would be useful outside of the crlf issue.
Ciao, Dscho