From: "Jay Soffian" <jaysoffian@gmail.com>
To: "Jeff King" <peff@peff.net>
Cc: "Junio C Hamano" <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] allow git-am to run in a subdirectory
Date: Sun, 2 Mar 2008 22:26:51 -0500 [thread overview]
Message-ID: <76718490803021926w29a6a44bha9fd22c48c94250a@mail.gmail.com> (raw)
In-Reply-To: <20080301081235.GA31855@coredump.intra.peff.net>
On Sat, Mar 1, 2008 at 3:12 AM, Jeff King <peff@peff.net> wrote:
> The problem is that I need to turn the original "$@" into a new "$@"
> that is correctly prefixed, which requires proper quoting.
Perhaps rev-parse could be taught to optionally convert relative
paths to absolute?
j.
next prev parent reply other threads:[~2008-03-03 3:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 6:22 [PATCH] allow git-am to run in a subdirectory Jeff King
2008-03-01 7:38 ` Junio C Hamano
2008-03-01 8:12 ` Jeff King
2008-03-01 8:15 ` Junio C Hamano
2008-03-01 8:20 ` Jeff King
2008-03-03 3:26 ` Jay Soffian [this message]
2008-03-03 6:46 ` Re* " Junio C Hamano
2008-03-03 6:58 ` Jeff King
2008-03-03 7:08 ` Junio C Hamano
2008-03-03 11:53 ` Johannes Schindelin
2008-03-03 17:01 ` Junio C Hamano
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=76718490803021926w29a6a44bha9fd22c48c94250a@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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 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).