From: Jeff King <peff@peff.net>
To: Philip Oakley <philipoakley@iee.org>
Cc: GitList <git@vger.kernel.org>
Subject: Re: [PATCH] Doc repository-layout: Show refs/replace
Date: Thu, 25 Oct 2012 06:34:14 -0400 [thread overview]
Message-ID: <20121025103413.GQ8390@sigill.intra.peff.net> (raw)
In-Reply-To: <1350852757-3924-1-git-send-email-philipoakley@iee.org>
On Sun, Oct 21, 2012 at 09:52:37PM +0100, Philip Oakley wrote:
> Signed-off-by: Philip Oakley <philipoakley@iee.org>
Thanks, this makes sense.
> +refs/replace/`<obj-sha1>`::
> + records the SHA1 of the object that replaces `<obj-sha1>`.
> + This is similar to info/grafts and is internally used and
> + maintained by `git replace`. Such refs can be exchanged between
> + repositories while grafts are not.
This should probably be an actual link to the git-replace manpage. I'll
convert it to a linkgit. No need to resend.
-Peff
prev parent reply other threads:[~2012-10-25 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-21 20:52 [PATCH] Doc repository-layout: Show refs/replace Philip Oakley
2012-10-25 10:34 ` Jeff King [this message]
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=20121025103413.GQ8390@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.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).