git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Luis Gutierrez <luis.gutierrez@xmos.com>
Cc: git@vger.kernel.org
Subject: Re: inted problems when upgrading to 1.6.0.4
Date: Tue, 25 Nov 2008 11:14:52 +0100	[thread overview]
Message-ID: <492BD01C.8070807@viscovery.net> (raw)
In-Reply-To: <492BC56A.6040506@xmos.com>

Luis Gutierrez schrieb:
> At my company we have been using git for the past months, and except for
> a few people, everyone is happy with it. Last week, we discovered that
> the mac version of git was misbehaving (v1.5.6.4), but upgrading the
> client to the latest one (v1.6.0.4) fixed the issue. Fearing consistency
> issue between version, I decided to update the version of the central
> repository (ie, the place were people can go and synchronize their code)
> on a RHEL4 box from 1.5.6.4 to 1.6.0.4.
> went to my git directory, pulled, checkout v1.6.0.4, and compiled with
> 'make --prefix=/usr/loca/ all' and installed with the same comamnd.

It's not necessarily the cause of your problems, but didn't make install
warn you:

        !! You have installed git-* commands to new gitexecdir.
        !! Old version git-* commands still remain in bindir.
        !! Mixing two versions of Git will lead to problems.
        !! Please remove old version commands in bindir now.

Did you do as you were told?

-- Hannes

  reply	other threads:[~2008-11-25 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25  9:29 inted problems when upgrading to 1.6.0.4 Luis Gutierrez
2008-11-25 10:14 ` Johannes Sixt [this message]
2008-11-25 10:20 ` Arafangion
     [not found]   ` <492BCFA0.5030708@xmos.com>
2008-11-25 10:54     ` Arafangion
2008-11-25 10:54       ` Luis Gutierrez
2008-11-25 11:14         ` Arafangion
2008-11-25 10:36 ` Brian Foster
2008-11-25 11:04 ` Johannes Sixt

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=492BD01C.8070807@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=git@vger.kernel.org \
    --cc=luis.gutierrez@xmos.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).