All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marius Storm-Olsen <marius@trolltech.com>
To: Nicolas Sebrecht <nicolas.s-dev@laposte.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] urls.txt: document optional port specification in git URLS
Date: Thu, 05 Feb 2009 10:12:35 +0100	[thread overview]
Message-ID: <498AAD83.9000200@trolltech.com> (raw)
In-Reply-To: <20090205083604.GC27983@ultras>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

Nicolas Sebrecht said the following on 05.02.2009 09:36:
> On Wed, Feb 04, 2009 at 12:51:35PM +0100, Stefan Naewe wrote:
>> +- git://host.xz{startsb}:port{endsb}/path/to/repo.git/
>> +- git://host.xz{startsb}:port{endsb}/~user/path/to/repo.git/
>>  - ssh://{startsb}user@{endsb}host.xz{startsb}:port{endsb}/path/to/repo.git/
>>  - ssh://{startsb}user@{endsb}host.xz/path/to/repo.git/
>>  - ssh://{startsb}user@{endsb}host.xz/~user/path/to/repo.git/
> 
> I did not understood. To what does '{startsb}' and '{endsb}' refer ?

Commands for the documentation tool
     {startsb} = Start/Left Square Bracket
     {endsb} = End/Right Square Bracket

so, you'll end up seeing
     - git://host.xz[:port]/path/to/repo.git/
     - git://host.xz[:port]/~user/path/to/repo.git/

-- 
.marius [@trolltech.com]
'if you know what you're doing, it's not research'


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

  reply	other threads:[~2009-02-05  9:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090205080913.GB27983@ultras>
2009-02-04 11:51 ` [PATCH] urls.txt: document optional port specification in git URLS Stefan Naewe
2009-02-04 18:09   ` Junio C Hamano
2009-02-04 20:49     ` [PATCH v2] " Stefan Naewe
2009-02-04 20:53       ` Junio C Hamano
2009-02-04 21:02         ` Stefan Näwe
2009-02-04 21:05           ` Junio C Hamano
2009-02-05  8:36   ` [PATCH] " Nicolas Sebrecht
2009-02-05  9:12     ` Marius Storm-Olsen [this message]
2009-02-05  8:41 ` Stefan Naewe

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=498AAD83.9000200@trolltech.com \
    --to=marius@trolltech.com \
    --cc=git@vger.kernel.org \
    --cc=nicolas.s-dev@laposte.net \
    /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.