git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Git Mailing List <git@vger.kernel.org>,
	Gabriel Filion <lelutin@gmail.com>,
	Junio C Hamano <gitster@pobox.com>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [RFC PATCH] Write new giturl(7) manpage
Date: Mon, 29 Mar 2010 22:35:12 +0530	[thread overview]
Message-ID: <f3271551003291005rf2d2e57p90dad68e451e1ff3@mail.gmail.com> (raw)
In-Reply-To: <fabb9a1e1003290859p25be2d7aqc7dcb46f3ec7ba4f@mail.gmail.com>

> One useful way of answering questions like this is to find the commits
> that added the <transport>::<address> syntax (probably easiest with git
> blame), and at the commits that touched urls.txt (probably with git log),
> and see if the reading the messages makes it obvious. I'd guess (without
> actually looking myself) that it was just overlooked.

Got it.

> Yup, my bad for not updating urls.txt (mainly because I didn't know it
> existed :P). I think Ramkumar's patch [0] to fix that is a step in the
> right direction :).

Thanks :) I've prepared a second revision, which is a complete rewrite
of urls. In the meantime, could you review this patch?

-- Ram

  reply	other threads:[~2010-03-29 17:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 14:59 [RFC PATCH] Write new giturl(7) manpage Ramkumar Ramachandra
2010-03-29 15:48 ` Daniel Barkalow
2010-03-29 15:55   ` Ilari Liusvaara
2010-03-29 15:59     ` Sverre Rabbelier
2010-03-29 17:05       ` Ramkumar Ramachandra [this message]
2010-03-29 19:18 ` Jonathan Nieder
2010-03-29 19:21   ` Sverre Rabbelier
2010-03-29 19:24   ` Ramkumar Ramachandra
2010-03-29 19:35     ` Ramkumar Ramachandra
2010-04-06  6:06     ` [PATCH/RFC] Documentation: reorganize documentation of URLs understood by git Jonathan Nieder
2010-04-06  6:57       ` Junio C Hamano
2010-04-06  7:40         ` Ramkumar Ramachandra
2010-04-06 21:33         ` 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=f3271551003291005rf2d2e57p90dad68e451e1ff3@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).