From: "Elijah Newren" <newren@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: "Johannes Sixt" <j.sixt@viscovery.net>,
"Jakub Narebski" <jnareb@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] upload-pack: Initialize the exec-path.
Date: Wed, 13 Feb 2008 06:00:33 -0700 [thread overview]
Message-ID: <51419b2c0802130500v9753ebeg934e2d02c9e363f7@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.1.00.0802121245140.3870@racer.site>
On Feb 12, 2008 5:45 AM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Tue, 12 Feb 2008, Johannes Schindelin wrote:
> > On Tue, 12 Feb 2008, Johannes Sixt wrote:
> > > Johannes Schindelin schrieb:
> > > > So, let's make git-upload-pack a builtin, no?
> > >
> > > How about this (almost) one-liner instead?
> >
> > I'm fine with it.
>
> But I also made this:
>
> -- snipsnap --
> [PATCH] Make upload-pack a builtin
>
> Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
<snip>
I tried this patch yesterday, but it seems to suffer from the same
problem? I had to manually apply the patch from Johannes Sixt on top
of this ("manually" since there was a trivial conflict) in order for
it to solve the problem.
Anyway, it works for me now. Thanks for the quick fixes!
Elijah
next prev parent reply other threads:[~2008-02-13 13:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 2:22 Unable to clone an ssh repository (with ugly installation-specific workaround) Elijah Newren
2008-02-12 7:04 ` David Symonds
2008-02-12 8:16 ` Jakub Narebski
2008-02-12 8:37 ` Johannes Sixt
2008-02-12 10:30 ` Johannes Schindelin
2008-02-12 11:28 ` [PATCH] upload-pack: Initialize the exec-path Johannes Sixt
2008-02-12 11:49 ` Johannes Schindelin
2008-02-12 12:45 ` Johannes Schindelin
2008-02-13 13:00 ` Elijah Newren [this message]
2008-02-13 12:57 ` Unable to clone an ssh repository (with ugly installation-specific workaround) Elijah Newren
2008-02-13 14:17 ` Stephen Sinclair
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=51419b2c0802130500v9753ebeg934e2d02c9e363f7@mail.gmail.com \
--to=newren@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=jnareb@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).