[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] STAT bits - Ouch!

To: Peter Slegg <p.slegg@scubadivers.co.uk>
Subject: Re: [MiNT] STAT bits - Ouch!
From: Alan Hourihane <alanh@fairlite.co.uk>
Date: Thu, 09 Dec 2010 13:42:14 +0000
Cc: mint <mint@lists.fishpool.fi>
In-reply-to: <000160df.01c69262b8b1@smtp.freeola.net>
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <1291852961.31976.28.camel@jetpack.demon.co.uk> <000160df.01c69262b8b1@smtp.freeola.net>
Sender: mint-bounce@lists.fishpool.fi

On Thu, 2010-12-09 at 13:08 +0200, Peter Slegg wrote:
> Do git and python use hard-coded values rather than the constants ?
> I am just curious why they cause a problem.

Python uses hard coded values that don't match the mintlib which will
cause problems.

git (which is a revision control system) stores these values within it's
database, so if a git repository is created on a different system and
pulled to a FreeMiNT system a mismatch occurs and it's unsharable
between the two. For an RCS, that's just horrible.

Alan.

Follow-Ups:
- Re: [MiNT] STAT bits - Ouch!
  - From: Konrad Kokoszkiewicz <draco@ibi.uw.edu.pl>

References:
- Re: [MiNT] STAT bits - Ouch!
  - From: Alan Hourihane <alanh@fairlite.co.uk>
- Re: [MiNT] STAT bits - Ouch!
  - From: Peter Slegg <p.slegg@scubadivers.co.uk>

Prev by Date: Re: [MiNT] STAT bits - Ouch!
Next by Date: Re: [MiNT] STAT bits - Ouch!
Previous by thread: Re: [MiNT] STAT bits - Ouch!
Next by thread: Re: [MiNT] STAT bits - Ouch!
Index(es):
- Date
- Thread