Dear diary, on Sat, Jul 23, 2005 at 01:26:07AM CEST, I got a letter
where Linus Torvalds <[EMAIL PROTECTED]> told me that...
> On Fri, 22 Jul 2005, Junio C Hamano wrote:
> > Linus Torvalds <[EMAIL PROTECTED]> writes:
> > 
> > > I'd _really_ prefer to not have any preferences or other metadata files
> > > under version control within that same project.
> > 
> > Don't you think that would be a per-project decision?  Is it
> > acceptable if I make sure that .gitinfo/* is _optional_ and
> > things do not break for projects that do not use it?
> It can't be a per-project decision, since the preferences are 
> per-developer.
> In other words, if it's per-project, then that implies that every single 
> developer has to agree on the same thing. Which just not possible - it 
> makes no sense.

Some example of possible per-project settings:

        pre-commit hook killing trailing whitespaces
        global per-project ignore file (*.ko or something)
        common base commit template
                (standardized form developer fills in when committing,
                 some remindments in the comment section, ...)

Obviously, you still ought to have a way to locally override any of
those per-repository in your .git/conf/.

                                Petr "Pasky" Baudis
If you want the holes in your knowledge showing up try teaching
someone.  -- Alan Cox
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to