On Fri, 22 Jul 2005, Junio C Hamano wrote:
> And the file would obviously be per-project, so according to
> Pasky's suggestion that would be ".gitinfo/fake_parents" ;-).

I'd _really_ prefer to not have any preferences or other metadata files
under version control within that same project.

If you want to version control them, that's fine, but don't tie the
versioning to the main project itself. You can have a _separate_ git
index, and a separate branch for the preferences and other metadata (but
you can, if you want to, obviously share the .git directory contents and
mix up the objects).

The thing is, different people might want to tie in these things different
ways. For example, one thing this kind of "grafting" is useful for is to
literally graft two different projects together, even if you may actually
want to export them independently (ie you do _not_ want the graftign
itself to be visible when you export it).

Think of something like a collection of projects, each under their own 
subdirectory. We could eventually literally make them _look_ like one big 
project, with cross-project commits grafted together, but they'd 
technically be totally independent (think "git" vs "gitk" - rather than 
having a very tight merge like I did, we could have tried to make it be a 
more virtual graft instead).

And personal preferences are just that - personal. I do _not_ want to have 
the kernel project history have things like "editor preferences" etc in 
the revision history - you might want to revision them, but that would be 
totally independent of the history of the project itself.

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to