All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Max Horn <max@quendi.de>
Cc: git@vger.kernel.org, spearce@spearce.org, jrnieder@gmail.com
Subject: Re: [PATCH] doc: add some crossrefs between manual pages
Date: Wed, 12 Nov 2014 12:58:49 -0800	[thread overview]
Message-ID: <xmqqbnoc3zli.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <96693472-344E-4ED3-B027-49A8303AF8C0@quendi.de> (Max Horn's message of "Wed, 12 Nov 2014 21:47:18 +0100")

Max Horn <max@quendi.de> writes:

> On 11.11.2014, at 23:51, Junio C Hamano <gitster@pobox.com> wrote:
> ...
>>> +linkgit:git-fast-import[1]
>> 
>> This looks somewhat out of place; fast-import is not the only or
>> even the primary way to do a remote-helper, is it?
>
> It depends on how you look at it, I'd say. If you write a remote-helper that
> uses the import/export feature, it is absolutely vital.  All remote helpers
> I ever worked on are of that kind, so to me it is the primary way ;-),
> although of course I realize there are others. So, how would you determine
> which of the various methods is the "primary" one?

You don't.  If there exists no clear "primary" one, you do not have
to designate a random one as the "primary".

I just thought that these references are to related/relevant pages
in the same family of commands, and not a place to list possible
implementation technologies.  We do not say "see also libcurl" only
because we have the curl-based remote helper that almost everybody
uses to interact with other repositories over https:// URLs here,
and do not list send-pack or receive-pack, even though the pair
would be a natural way to implement 'fetch' and 'push' methods to a
helper to interact with a native Git repository, either.

  reply	other threads:[~2014-11-12 20:58 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 [this message]
2014-11-12 21:07       ` Junio C Hamano
2014-12-09 17:14         ` Jonathan Nieder

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=xmqqbnoc3zli.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.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.