From: "Dan McGee" <dan@archlinux.org>
To: "Jeff King" <peff@peff.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH] send-pack: respect '+' on wildcard refspecs
Date: Fri, 19 Oct 2007 20:00:37 -0500 [thread overview]
Message-ID: <449c10960710191800j3e61b80cma2c582080c1dd07c@mail.gmail.com> (raw)
In-Reply-To: <20071019134339.GA21852@coredump.intra.peff.net>
On 10/19/07, Jeff King <peff@peff.net> wrote:
> On Fri, Oct 19, 2007 at 08:38:06AM -0500, Dan McGee wrote:
>
> > origin(junio)/master: 58ba4f6
> > origin(junio)/next: fe96ee67ec5840
> > spearce/master: 7840ce6cb24a9d
> > spearce/next: 2fe5433b416f0df
> >
> > Can you let me know what commit you based the patch off of? I'm at
> > work for the next 8 hours or so, so I can't look in to this a whole
> > lot until tonight.
>
> It is based on Shawn's next, 2fe5433b. Are you sure you're not doing
> something silly like executing an older version of git that is in your
> PATH?
Turns out I didn't have GIT_EXEC_PATH set up right. Once I do that,
everything seems to work just fine.
Thanks for looking into this Jeff, and git-bisect just won me over. It
made easy work of finding the commit that broke this.
-Dan
next prev parent reply other threads:[~2007-10-20 1:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 9:04 [PATCH] send-pack: respect '+' on wildcard refspecs Jeff King
2007-10-19 9:04 ` Jeff King
2007-10-19 12:10 ` Dan McGee
2007-10-19 12:27 ` Jeff King
2007-10-19 13:38 ` Dan McGee
2007-10-19 13:43 ` Jeff King
2007-10-19 14:11 ` Dan McGee
2007-10-20 1:00 ` Dan McGee [this message]
2007-10-20 4:22 ` Jeff King
2007-10-20 4:57 ` Shawn O. Pearce
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=449c10960710191800j3e61b80cma2c582080c1dd07c@mail.gmail.com \
--to=dan@archlinux.org \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=spearce@spearce.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).