From: Jonathan Nieder <jrnieder@gmail.com>
To: Geoff Russell <geoffrey.russell@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Thomas Rast <trast@student.ethz.ch>
Subject: [PATCH/RFC] Documentation: add a FILES section for show-ref
Date: Sun, 8 Aug 2010 20:32:43 -0500 [thread overview]
Message-ID: <20100809013243.GA9385@burratino> (raw)
In-Reply-To: <AANLkTi=J3tDnZUg3k5bzDk2ydzYVVLKLwoW0gpBypYAs@mail.gmail.com>
A peek at where the refs are kept might help understanding, even if,
as the DESCRIPTION section suggests, direct access is not part of the
public API.
Balance that out with a pointer to update-ref.
Suggested-by: Geoff Russell <geoffrey.russell@gmail.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
---
Documentation/git-show-ref.txt | 7 ++++++-
1 files changed, 6 insertions(+), 1 deletions(-)
diff --git a/Documentation/git-show-ref.txt b/Documentation/git-show-ref.txt
index 3f9d9c6..3fe961d 100644
--- a/Documentation/git-show-ref.txt
+++ b/Documentation/git-show-ref.txt
@@ -163,9 +163,15 @@ flag, so you can do
to get a listing of all tags together with what they dereference.
+FILES
+-----
+`.git/refs/*`, `.git/packed-refs`
+
SEE ALSO
--------
-linkgit:git-ls-remote[1]
+linkgit:git-ls-remote[1],
+linkgit:git-update-ref[1],
+linkgit:gitrepository-layout[5]
AUTHORS
-------
--
1.7.2.1.544.ga752d.dirty
next prev parent reply other threads:[~2010-08-09 1:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-09 1:17 understanding how remote tracking works Geoff Russell
2010-08-09 1:31 ` Ralf Ebert
2010-08-09 1:53 ` Geoff Russell
2010-08-09 2:13 ` Michael Witten
2010-08-09 2:19 ` Jonathan Nieder
2010-08-09 3:46 ` Geoff Russell
2010-08-09 19:31 ` Junio C Hamano
2010-08-09 20:53 ` Jonathan Nieder
2010-08-09 23:07 ` discarding refs/original/* after filter-branch (Re: understanding how remote tracking works) Jonathan Nieder
2010-08-09 1:32 ` Jonathan Nieder [this message]
2010-08-09 19:33 ` [PATCH/RFC] Documentation: add a FILES section for show-ref 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=20100809013243.GA9385@burratino \
--to=jrnieder@gmail.com \
--cc=geoffrey.russell@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@student.ethz.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.