Re: .gitignore, .gitattributes, .gitmodules, .gitprecious?, .gitacls? etc.
- From
- Dmitry Kakurin <dmitry.kakurin@gmail.com>
- Date
- Aug 26, 2007, 06:36 UTC
- Message-ID
- <C22431BFCD8E403FA10C8E91DE8AC19A@ntdev.corp.microsoft.com>
- In-Reply-To
- <7vsl66svv4.fsf@gitster.siamese.dyndns.org>
----- Original Message ----- From: "Junio C Hamano" <gitster@pobox.com>
>> Can you specify _exactly_ how it works now? And I'll show you a bunch of corner cases where it's broken. > > As I made it clear, it is a compromise. I am not interested in > discussing corner cases with you -- I am sure there are.
Usually many corner cases == design flaw.
> If you are offering improvements, I am all ears.
I thought I did: I've observed that these problem are caused by storing metadata in regular files (that exist both in repo/index and in workplace). My knowledge of Git internals is quite limited, but if *I* were to do it right now, I'd introduce a META entry in every TREE object that would point to a BLOB that contains combined content of .gitattributes, .gitignore etc. Then command like 'git meta' would open vi for this BLOB, let you edit it, and then would upload it back to index.
- Dmitry