git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Gabriel Filion <lelutin@gmail.com>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 2/5] Documentation/urls: Rewrite to accomodate  <transport>::<address>
Date: Sun, 18 Apr 2010 09:29:54 +0530	[thread overview]
Message-ID: <i2gf3271551004172059sb3abbafcz2feb9eed14e596aa@mail.gmail.com> (raw)
In-Reply-To: <20100418025940.GA2249@progeny.tock>

Hi,

> Hmm: if it is not built in to the git binary, is it right to call the
> support native?  I don’t mean to say HTTP support is a second-class
> citizen (with http-backend on the server side, it isn’t any more), but
> it is possible that remote-http is not installed on a system.  Also, it
> is a good example to introduce remote helpers with.

By "native", I meant that no special remote helpers are necessary (it
would be with svn, for example). Does the technical detail of whether
the support is built into the main Git binary need to enter the
documentation?

Thanks for the review! :) I'll post a fixup patch soon.

-- Ram

  reply	other threads:[~2010-04-18  4:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-18  0:54 [PATCH 2/5] Documentation/urls: Rewrite to accomodate <transport>::<address> Ramkumar Ramachandra
2010-04-18  2:59 ` Jonathan Nieder
2010-04-18  3:59   ` Ramkumar Ramachandra [this message]
2010-04-18  5:03   ` Ramkumar Ramachandra
2010-04-18 18:39     ` Junio C Hamano
2010-04-18 18:44       ` Sverre Rabbelier
2010-04-18 20:59         ` Junio C Hamano
2010-04-18 21:10           ` Sverre Rabbelier
2010-04-18 21:56             ` 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=i2gf3271551004172059sb3abbafcz2feb9eed14e596aa@mail.gmail.com \
    --to=artagnon@gmail.com \
    --cc=barkalow@iabervon.org \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ilari.liusvaara@elisanet.fi \
    --cc=jrnieder@gmail.com \
    --cc=lelutin@gmail.com \
    --cc=srabbelier@gmail.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).