git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Hellmuth <hellmuth@ira.uka.de>
To: Neal Kreitzinger <nkreitzinger@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Neal Kreitzinger <neal@rsss.com>,
	git@vger.kernel.org
Subject: Re: git compiled on same distro, different versions
Date: Mon, 27 Feb 2012 16:19:56 +0100	[thread overview]
Message-ID: <4F4B9F1C.8040607@ira.uka.de> (raw)
In-Reply-To: <4F4825CA.1060506@gmail.com>

On 25.02.2012 01:05, Neal Kreitzinger wrote:
> "high-level" question:
> If I compile git 1.7.9.2 (from git.git source) on RHEL6 test-box and
> test it and conclude that it "works right" is that sufficient for me to
> then go ahead and compile git 1.7.9.2 on RHEL5 real-box and
> expect/assume that it will also "work right"? IOW, will they produce the
> same results? Because if not then I have just potentially broken the
> real-box.

Depends on your thoroughness. I.e. you have to assume that your testing 
does actually test aspects that are not covered by all the tests 
included with git (and not detected by hundreds of other users on that 
platform). In that case you can't guarantee anything, even applying 
routine security patches to the operating system could potentially break 
things (and some companies really test every single patch they apply to 
mission-critical systems).

> "low-level" question:
> I suspect git calls linux commands alot. Git has "plumbing" commands
> that are not supposed to "break" scripts. Does linux also have
> "plumbing" commands that are not supposed to "break" scripts? Does git
> only use linux "plumbing" commands? Because if git commands uses linux
> "porcelain" then the linux "porcelain" change could cause git to change
> (not necessarily "break"). Maybe git-porcelain only uses
> linux-porcelain, and git-plumbing only uses linux-plumbing.

As far as I know there is no plumbing/porcelain distinction in the linux 
kernel. But while the internal interfaces in the kernel change a lot, 
the external interface (to user space programs like git) is relatively 
fixed. You can assume that git is adapted to incompatible changes very 
fast. But nobody can guarantee you that bugs won't make a difference 
going from one platform to another.

      reply	other threads:[~2012-02-27 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 21:05 git compiled on same distro, different versions Neal Kreitzinger
2012-02-24 22:08 ` Junio C Hamano
2012-02-25  0:05   ` Neal Kreitzinger
2012-02-27 15:19     ` Holger Hellmuth [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=4F4B9F1C.8040607@ira.uka.de \
    --to=hellmuth@ira.uka.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=neal@rsss.com \
    --cc=nkreitzinger@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).