Re: [Gnu-arch-users] How to support arch on systems with a small PATH_MAX [WAS: arch o n windows?]

[John Meinel]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, I think your definition is accurate, and theirs is wrong. I think
the change, if it has a flag, will be backwards compatible, but old
versions of tla won't be able to read the new format of the archive.

John
=:->

Ron Parker wrote:

| On Thu, 15 Jul 2004 06:25:38 +0200, address@hidden <address@hidden> wrote:
|
|>pathnames like
|>
|>category/category--branch/category--branch--version/
|>and
|>category/branch/version/
|>
|>can friendly coexist without breaking upward compatibility.
|>all which needs to be done:
|
|
| Okay, perhaps I need someone who knows what it means to define upwards
| compatible for me.  I have not been able to find a good definition of
| it on the Net.  I know what backwards compatible means. I've even seen
| and understand forward compatible.  But I inferred a meaning for
| upwards compatible from seeing it used on this list.
|
| In my original post I (mis)used upwards compatible to mean introducing
| changes to tla in such a way that older binaries would be able to work
| with the newer data, without change. So please take this into account
| when (re)reading my post.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFA9r3DJdeBCYSNAAMRAh6kAJ44eylJlYtGKJRObexI85hdLwbrWwCgxB/5
XixOXnzv6wOIEuRF0xJ6NP4=
=5Vd2
-----END PGP SIGNATURE-----