Jakub Narebski wrote:
Andreas Ericsson wrote:
Shawn Pearce wrote:
I already assume/know that refs/heads and refs/tags are completely
off-limits as they are for user refs only.
I also think the core GIT tools already assume that anything
directly under .git which is strictly a file and which is named
entirely with uppercase letters (aside from "HEAD") is strictly a
temporary/short-lived state type item (e.g. COMMIT_MSG) used by a
Porcelain.
But is saying ".git/refs/eclipse-workspaces" is probably able to
be used for this purpose safe? :-)
.git/eclipse/whatever-you-like
would probably be better. Heads can be stored directly under .git/refs
too. Most likely, nothing will ever be stored under ./git/eclipse by
either core git or the current (other) porcelains though.
I think if it is a ref, which one wants to be visible to git-fsck (and
git-prune), it should be under .git/refs.
Yes, but I understood him to mean "it's a tree-sha" instead of a
branch/head thing, which would mean it doesn't fit the .git/refs
definition of ref.
--
Andreas Ericsson andreas.ericsson@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
: 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