From: Namhyung Kim <namhyung@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-remote.txt: fix wrong remote refspec
Date: Fri, 24 Jun 2011 01:03:06 +0900 [thread overview]
Message-ID: <1308844986.1332.10.camel@leonhard> (raw)
In-Reply-To: <7vy60s36mm.fsf@alter.siamese.dyndns.org>
2011-06-23 (목), 08:33 -0700, Junio C Hamano:
> And here is my attempt, on top of Namhyung's v2 of this patch.
>
> -- >8 --
> Subject: git-remote.txt: avoid sounding as if loose refs are the only ones in the world
>
> It was correct to say "The file $GIT_DIR/refs/heads/master stores the
> commit object name at the tip of the master branch" in the older days,
> but not anymore, as refs can be packed into $GIT_DIR/packed-refs file.
>
> Update the document to talk in terms of a more abstract concept "ref" and
> "symbolic ref" where we are not describing the underlying implementation
> detail.
>
> This on purpose leaves two instances of $GIT_DIR/ in the git-remote
> documentation; they do talk about $GIT_DIR/remotes/ and $GIT_DIR/branches/
> file hierarchy that used to be the place to store configuration around
> remotes before the configuration mechanism took them over.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
By quick grep-ing $GIT_DIR/refs/, I found git.txt and
glossary-content.txt might need the same treatment. Did/Could you check
out those too?
Otherwise, looks good to me.
Thanks.
--
Regards,
Namhyung Kim
next prev parent reply other threads:[~2011-06-23 16:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-23 4:45 [PATCH] git-remote.txt: fix wrong remote refspec Namhyung Kim
2011-06-23 5:35 ` Junio C Hamano
2011-06-23 6:17 ` Namhyung Kim
2011-06-23 8:12 ` [PATCH v2] " Namhyung Kim
2011-06-23 15:33 ` [PATCH] " Junio C Hamano
2011-06-23 16:03 ` Namhyung Kim [this message]
2011-06-23 16:52 ` [PATCH 0/5] Clarify "refs" Junio C Hamano
2011-06-23 16:52 ` [PATCH 1/5] check-ref-format doc: de-emphasize the implementation detail of a ref Junio C Hamano
2011-06-23 22:14 ` Eric Sunshine
2011-06-23 16:52 ` [PATCH 2/5] git.txt: " Junio C Hamano
2011-06-23 16:52 ` [PATCH 3/5] glossary: update description of "tag" Junio C Hamano
2011-06-23 22:19 ` Eric Sunshine
2011-06-23 16:52 ` [PATCH 4/5] glossary: update description of head and ref Junio C Hamano
2011-06-23 16:52 ` [PATCH 5/5] glossary: clarify description of HEAD Junio C Hamano
2011-06-23 17:06 ` Carlos Martín Nieto
2011-06-23 17:12 ` 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=1308844986.1332.10.camel@leonhard \
--to=namhyung@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).