git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
* Just a note: .git/refs/snap/ is not standard
@ 2005-05-02  1:54 Junio C Hamano
  2005-05-02  3:13 ` Daniel Barkalow
  0 siblings, 1 reply; 2+ messages in thread
From: Junio C Hamano @ 2005-05-02  1:54 UTC (permalink / raw
  To: Linus Torvalds; +Cc: git

Linus, 

    not that there is any "de facto" or any standard there, but
the name .git/refs/snap/ you lifted from the vicinity thing is
not something Cogito folks have.  My understanding is of their
concensus is that .git/refs have single level subdirectories
like 'heads' and 'tags', and there will be little 41-byte text
files that look like .git/HEAD.  So you probably would want to
either (1) readdir in .git/refs (to future proof) or (2) drop
refs/snap from the vicinity list for now (to not give special
treatment to JIT, which I myself do not mind ;-)).  Also if you
go route (2) drop "refs" itself as well.


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Just a note: .git/refs/snap/ is not standard
  2005-05-02  1:54 Just a note: .git/refs/snap/ is not standard Junio C Hamano
@ 2005-05-02  3:13 ` Daniel Barkalow
  0 siblings, 0 replies; 2+ messages in thread
From: Daniel Barkalow @ 2005-05-02  3:13 UTC (permalink / raw
  To: Junio C Hamano; +Cc: Linus Torvalds, git

On Sun, 1 May 2005, Junio C Hamano wrote:

> Linus, 
> 
>     not that there is any "de facto" or any standard there, but
> the name .git/refs/snap/ you lifted from the vicinity thing is
> not something Cogito folks have.  My understanding is of their
> concensus is that .git/refs have single level subdirectories
> like 'heads' and 'tags', and there will be little 41-byte text
> files that look like .git/HEAD.

I was intending this to be a more general concensus (and you seem to have
followed it with your "snap" subdirectory).

> So you probably would want to either (1) readdir in .git/refs (to future
> proof) or (2) drop refs/snap from the vicinity list for now (to not give
> special treatment to JIT, which I myself do not mind ;-)).  Also if you
> go route (2) drop "refs" itself as well.

Actually, my code was intended to take things like "heads/master" or
"tags/linux-2.6.13", which are found under "refs/" (although I also check
that they don't start with "." and have exactly one "/", to enforce the
naming system). Making it "heads/linus" rather than "linus" is important
for writing the files, since you can't guess reliably what subdirectory
the user means; also, it is easier for dealing with HTTP servers, where
you don't know what to ask for.

	-Daniel
*This .sig left intentionally blank*


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-05-02  3:07 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-02  1:54 Just a note: .git/refs/snap/ is not standard Junio C Hamano
2005-05-02  3:13 ` Daniel Barkalow

Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).