From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Björn Steinbrink" <B.Steinbrink@gmx.de>,
"Eli Barzilay" <eli@barzilay.org>, git <git@vger.kernel.org>
Subject: Re: Feature request: relative paths
Date: Thu, 6 May 2010 05:09:33 -0400 [thread overview]
Message-ID: <20100506090933.GC31873@coredump.intra.peff.net> (raw)
In-Reply-To: <20100506090132.GA26079@progeny.tock>
On Thu, May 06, 2010 at 04:01:33AM -0500, Jonathan Nieder wrote:
> I suggest reviving Dscho’s :./ syntax[1].
> [1] http://thread.gmane.org/gmane.comp.version-control.git/68786/focus=68905
Oops, I was wrong about "there is no patch" (apparently I even submitted
a followup!).
Yes, I think that patch is a sane start, but it needs some cleanup.
-Peff
next prev parent reply other threads:[~2010-05-06 9:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 6:01 Feature request: relative paths Eli Barzilay
2010-05-06 8:31 ` Jonathan Nieder
2010-05-06 8:46 ` Björn Steinbrink
2010-05-06 9:01 ` Jonathan Nieder
2010-05-06 9:09 ` Jeff King [this message]
2010-05-06 9:04 ` Jeff King
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=20100506090933.GC31873@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=B.Steinbrink@gmx.de \
--cc=eli@barzilay.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@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).