git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@ucw.cz>
To: Inaky Perez-Gonzalez <inaky@linux.intel.com>
Cc: tony.luck@intel.com, Linus Torvalds <torvalds@osdl.org>,
	linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
	git@vger.kernel.org
Subject: Re: ia64 git pull
Date: Fri, 22 Apr 2005 03:53:40 +0200	[thread overview]
Message-ID: <20050422015340.GD7443@pasky.ji.cz> (raw)
In-Reply-To: <17000.22515.170455.192374@sodium.jf.intel.com>

Dear diary, on Fri, Apr 22, 2005 at 03:48:35AM CEST, I got a letter
where Inaky Perez-Gonzalez <inaky@linux.intel.com> told me that...
> >>>>> Petr Baudis <pasky@ucw.cz> writes:
> 
> > I've just added to git-pasky a possibility to refer to branches
> > inside of repositories by a fragment identifier:
> 
> > rsync://rsync.kernel.org/pub/scm/linux/kernel/git/aegl/linux-2.6.git#testing
> 
> > will refer to your testing branch in that repository.
> 
> Can we use something other than #? we'll have to scape it all the time
> in the shell (or at least also allow some other char, something
> without special meta-character meaning in the shell, like %).

Remember that it's an URL (so you can't use '%'), and '#' is the
canonical URL fragment identifier delimiter. (And fragments are perfect
for this kind of thing, if you look at the RFC, BTW.)

Still, why would you escape it? My shell will not take # as a comment
start if it is immediately after an alphanumeric character.

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor

  parent reply	other threads:[~2005-04-22  1:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200504212042.j3LKgng04318@unix-os.sc.intel.com>
     [not found] ` <Pine.LNX.4.58.0504211403080.2344@ppc970.osdl.org>
     [not found]   ` <200504212155.j3LLtho04949@unix-os.sc.intel.com>
     [not found]     ` <Pine.LNX.4.58.0504211520250.2344@ppc970.osdl.org>
2005-04-21 22:58       ` ia64 git pull Petr Baudis
     [not found]     ` <200504212301.j3LN1Do05507@unix-os.sc.intel.com>
     [not found]       ` <20050422012546.GD1474@pasky.ji.cz>
     [not found]         ` <17000.22515.170455.192374@sodium.jf.intel.com>
2005-04-22  1:53           ` Petr Baudis [this message]
2005-04-22  2:06             ` Inaky Perez-Gonzalez
2005-04-22  3:30               ` David A. Wheeler

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=20050422015340.GD7443@pasky.ji.cz \
    --to=pasky@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=inaky@linux.intel.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tony.luck@intel.com \
    --cc=torvalds@osdl.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 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).