From: "Josef 'Jeff' Sipek" <jeffpc@josefsipek.net>
To: Alex Chiang <achiang@hp.com>, git@vger.kernel.org
Subject: Re: [PATCH] guilt(1): fix path to git-sh-setup
Date: Thu, 17 Jul 2008 10:53:56 -0400 [thread overview]
Message-ID: <20080717145356.GA7235@josefsipek.net> (raw)
In-Reply-To: <20080716232339.GC22919@ldl.fc.hp.com>
On Wed, Jul 16, 2008 at 05:23:39PM -0600, Alex Chiang wrote:
> git is in the process of moving subcommands to /usr/libexec/git-core
>
> This move breaks an assumption in guilt about the location of
> git-sh-setup.
I already have a fix for this queued up.
Thanks anyway,
Josef 'Jeff' Sipek.
P.S. Pasky: good catch, I'll check the queued up patch to make sure it's not
"broken"
--
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like
that.
- Linus Torvalds
prev parent reply other threads:[~2008-07-17 14:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 23:23 [PATCH] guilt(1): fix path to git-sh-setup Alex Chiang
2008-07-17 10:02 ` Petr Baudis
2008-07-17 11:58 ` Johannes Schindelin
2008-07-17 14:53 ` Josef 'Jeff' Sipek [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=20080717145356.GA7235@josefsipek.net \
--to=jeffpc@josefsipek.net \
--cc=achiang@hp.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).