From: David Miller <davem@davemloft.net>
To: gitster@pobox.com
Cc: git@vger.kernel.org
Subject: Re: setup_path()
Date: Wed, 13 Feb 2008 17:54:05 -0800 (PST) [thread overview]
Message-ID: <20080213.175405.10792562.davem@davemloft.net> (raw)
In-Reply-To: <7v3arwpqxj.fsf@gitster.siamese.dyndns.org>
From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 13 Feb 2008 12:00:40 -0800
> Yeah, Johannes Sixt had a patch to do exactly that earlier
>
> Message-ID: <47B182C1.60006@viscovery.net>
> http://news.gmane.org/gmane.comp.version-control.git/73651
>
> and I think it is a good idea to apply it.
Me too.
In fact people can easily end up unintentionally using different
versions of GIT. For example in my case I had the distribution's GIT
installed in /usr/bin/git et al., then I installed the current
upstream version of GIT in my home directory.
A different version of GIT gets used when you run things locally
vs. doing things remotely over SSH. And I didn't notice this until I
uninstalled the git-core package on my system.
prev parent reply other threads:[~2008-02-14 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-13 12:49 setup_path() David Miller
2008-02-13 20:00 ` setup_path() Junio C Hamano
2008-02-14 1:54 ` David Miller [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=20080213.175405.10792562.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).