From: Alex Riesen <raa.lkml@gmail.com>
To: David Reiss <dreiss@facebook.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/4] Implement normalize_absolute_path
Date: Thu, 22 May 2008 14:48:54 +0200 [thread overview]
Message-ID: <20080522124854.GC3206@steel.home> (raw)
In-Reply-To: <4833DE89.4000106@facebook.com>
David Reiss, Wed, May 21, 2008 10:34:17 +0200:
> This is close enough to what I want that I could definitely use it if it
> were in the main tree. I read through most of that thread, but I
> couldn't figure out what ever happened to your patch. (I couldn't find
> a clear rejection, but I also don't see it in master.)
Me too. OTOH, it was not a clear proposal for inclusion.
prev parent reply other threads:[~2008-05-22 12:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-20 6:48 [PATCH 1/4] Implement normalize_absolute_path David Reiss
2008-05-20 12:22 ` Johannes Schindelin
2008-05-20 16:44 ` David Reiss
2008-05-20 22:24 ` Alex Riesen
2008-05-21 8:34 ` David Reiss
2008-05-22 12:48 ` Alex Riesen [this message]
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=20080522124854.GC3206@steel.home \
--to=raa.lkml@gmail.com \
--cc=dreiss@facebook.com \
--cc=git@vger.kernel.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).