From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Items not covered by repository-layout.txt
Date: Mon, 10 Jul 2006 22:46:02 +0200 [thread overview]
Message-ID: <e8ue98$o7t$1@sea.gmane.org> (raw)
I have noticed few files in .git/ directory which currently are not covered
(and neither is their format) by Documentation/repository-layout.txt
* COMMIT_EDITMSG (temporary file, when I decided during writing commit
message that I should change something before commit)
* FETCH_HEAD (format?)
* HEAD, ORIG_HEAD and probably some other *_HEAD
* .tmp-vtag (I'm not sure what have left that, probably git-verify-tag
broken due to lack of signing PGP keys)
* description file
I know they are fairly obvious, but having everything that one could fing in
his/her git-core managed .git repository would be nice...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next reply other threads:[~2006-07-10 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-10 20:46 Jakub Narebski [this message]
2006-07-10 21:29 ` Items not covered by repository-layout.txt Junio C Hamano
2006-07-10 21:42 ` Jakub Narebski
2006-07-11 0:23 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e8ue98$o7t$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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 NNTP newsgroup(s).