Re: .gitignore, .gitattributes, .gitmodules, .gitprecious?, .gitacls? etc.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



----- Original Message ----- From: "Junio C Hamano" <gitster@xxxxxxxxx>
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

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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux