From: "Matt Graham" <mdg149@gmail.com>
To: rjtaylor@havocinspired.co.uk
Cc: git@vger.kernel.org
Subject: Re: Different Versions
Date: Thu, 24 Apr 2008 10:57:19 -0400 [thread overview]
Message-ID: <1c5969370804240757i1349432at55fb2a7aeae1da63@mail.gmail.com> (raw)
In-Reply-To: <899199.2868131209043100219.JavaMail.servlet@kundenserver>
I've always had trouble when dev servers and live servers have
differences. Apart from how well 1.4 and 1.5 might work with
eachother, I'd recommend building from latest stable (1.5.5.1) on both
machines anyway. I build on 7.10 and the 2-line default instructions
at the top of git/INSTALL work pretty well.
I get an error if I try to build the info, so just leave out the info
and install-info, and it should be ok.
On Thu, Apr 24, 2008 at 9:18 AM, <rjtaylor@havocinspired.co.uk> wrote:
> Hi,
>
> First post, hope this is going to the right place.
>
> I'm in a fairly restricted situation were I have a Live Web Server and a Dev Web Server. Now the Live box is running Ubuntu 7.04, and installs git version 1.4.* through apt-get. On the Dev box I've got Ubuntu 7.10, and this installs git version 1.5.*.
>
> Each seem to use slightly different commands, e.g. to initialise a repository.
>
> My question is am I ok to use git versions 1.4.* and 1.5.* together, or am I going to have problems? Should I down great my Dev box to Ubuntu 7.04 to get git version 1.4* so they are the same?
>
> I can't take down the Live box, or upgrade git on it, hence the fairly restricted situation.
>
> Any advice would be appreciated.
>
> Regards
>
> Ryan
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-04-24 14:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 13:18 Different Versions rjtaylor
2008-04-24 14:57 ` Matt Graham [this message]
2008-04-24 19:50 ` Alex Riesen
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=1c5969370804240757i1349432at55fb2a7aeae1da63@mail.gmail.com \
--to=mdg149@gmail.com \
--cc=git@vger.kernel.org \
--cc=rjtaylor@havocinspired.co.uk \
/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).