From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Max Horn <max@quendi.de>, git@vger.kernel.org, spearce@spearce.org
Subject: Re: [PATCH] doc: add some crossrefs between manual pages
Date: Tue, 9 Dec 2014 09:14:38 -0800 [thread overview]
Message-ID: <20141209171438.GA22606@google.com> (raw)
In-Reply-To: <xmqq7fz03z7i.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
> So I am OK to special case fast-import and single it out as a
> notable implementation technology, which is what your patch does.
More importantly, helpers implementing the "import" or "export"
capability are indicating that they grok the fast-import format. What
they use behind the scenes to produce or parse it is not so important
--- the relevant thing is that a fast-import stream (with format
documented in git-fast-import(1)) is part of the remote helper
protocol in this case.
Thanks,
Jonathan
prev parent reply other threads:[~2014-12-09 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-11 20:17 [PATCH] doc: add some crossrefs between manual pages Max Horn
2014-11-11 22:51 ` Junio C Hamano
2014-11-12 20:47 ` Max Horn
2014-11-12 20:58 ` Junio C Hamano
2014-11-12 21:07 ` Junio C Hamano
2014-12-09 17:14 ` Jonathan Nieder [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=20141209171438.GA22606@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=max@quendi.de \
--cc=spearce@spearce.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 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.