From: Hendrik Visage <hvjunk@gmail.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: david@dgreaves.com, git@vger.kernel.org
Subject: Re: git vs git
Date: Tue, 31 Jan 2006 07:05:55 +0200 [thread overview]
Message-ID: <d93f04c70601302105v426201dbhac6abd41cdc4050c@mail.gmail.com> (raw)
In-Reply-To: <46a038f90601301216n793f0eb5k34a2b5a7c4e7491e@mail.gmail.com>
On 1/30/06, Martin Langhoff <martin.langhoff@gmail.com> wrote:
> On 1/31/06, Hendrik Visage <hvjunk@gmail.com> wrote:
> > git isn't
> > working because the wrong git is in the right place :(
>
> Well, I just hit this yesterday on a colleage's machine who was trying
> to get going with git.His first try was to `apt-get install git` and
> as that didn't lead anywhere he fetched the git (scm) sources and
> built them.
>
<snip>
> Not sure how to deal with this. Packages already record (or can
> record) it as a conflict, but source built stuff is different. Perhaps
> during `make install` we should try and exec git --version towards the
> end and print a big fat warning?
Or stop the egos and do a name change as would be the honourable way
especially as gitscm is less than a year old...
--
Hendrik Visage
prev parent reply other threads:[~2006-01-31 5:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 15:14 git vs git Hendrik Visage
2006-01-30 15:18 ` David Lang
2006-01-30 15:30 ` Josh Boyer
2006-01-30 15:37 ` Erik Mouw
2006-01-30 16:09 ` Hendrik Visage
2006-01-30 16:26 ` Johannes Schindelin
2006-01-30 16:55 ` Randal L. Schwartz
2006-01-30 17:23 ` Erik Mouw
2006-01-30 19:22 ` Junio C Hamano
2006-01-30 20:16 ` Martin Langhoff
2006-01-31 5:05 ` Hendrik Visage [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=d93f04c70601302105v426201dbhac6abd41cdc4050c@mail.gmail.com \
--to=hvjunk@gmail.com \
--cc=david@dgreaves.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@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).