From: Junio C Hamano Date: Tue, 03 May 2005 04:15:43 GMT Subject: Re: [PATCH] Add exclude file support to cg-status Message-ID: <7v4qdlndw0.fsf@assigned-by-dhcp.cox.net> In-Reply-To: <20050502193343.A25462@cox.net> >>>>> "MP" == Matt Porter writes: MP> My reasoning for not doing something like this was that there is MP> only ever one exclude file. In other instances of cogito specific MP> data in the .git directory, there is a subdir named for the class MP> of data being stored there (i.e. branches, refs). In this case, MP> it didn't seem necessary. On the other hand, this made me MP> wonder whether there should just be a .git/cginfo subdir where MP> exclude, branches, refs, etc. all live under since they are MP> cogito specfic functionality. Something like: MP> .git/cginfo/ MP> exclude MP> branches/ MP> refs/ MP> and so on... You may want to check the past thread, like this one: From: Daniel Barkalow To: Junio C Hamano cc: David Greaves , GIT Mailing Lists Subject: Re: [PATCh] jit-trackdown Message-ID: On Fri, 29 Apr 2005, Junio C Hamano wrote: > Have toilet side gitters reached a concensus (or semi-concensus) > on how things under .git/ should be organized? Is there a > summary somewhere, something along the following lines? I've made a proposal like the following: .git/ objects/ (traditional) refs/ Directories of hex SHA1 + newline files heads/ Commits which are heads of various sorts tags/ Tags, by the tag name (or some local renaming of it) info/ Other shared information remotes ... Everything else isn't shared HEAD Symlink to refs/heads/ The plumbing doesn't care what you name heads or tags, but expects things to be in heads to be commit objects and tags to be tag objects (which can tag whatever). AFAICT, there is general concensus that this is how things should be, but I haven't convinced Linus that the plumbing should know about anything other than objects/. -Daniel