To: chth@gmx.net
References: <87brf8u340.fsf@tleepslib.sk.tsukuba.ac.jp>
	<20041012080350.730e5891@comet>
From: Miles Bader <miles@lsi.nec.co.jp>
System-Type: i686-pc-linux-gnu
Blat: Foop
Date: Tue, 12 Oct 2004 15:18:02 +0900
In-Reply-To: <20041012080350.730e5891@comet> (chth@gmx.net's message of
	"Tue, 12 Oct 2004 08:03:50 +0200")
Message-ID: <buosm8kihnp.fsf@mctpc71.ucom.lsi.nec.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: gnu-arch-users@gnu.org
Subject: [Gnu-arch-users] Re: Is tagline an attractive nuisance for
	international users?
Precedence: list
Reply-To: Miles Bader <miles@gnu.org>
Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org
Status: RO
Content-Length: 1142
Lines: 25
chth@gmx.net writes:
> Someone on IRC had concerns about taglines being affected by Search and
> Replace actions.

"Concerns"?  As in it happened to them, or they just thought "Oh maybe
it could happen"?  If it did happen, was it with a UUID-style tagline,
or an "old style" lots-of-random-info tagline?

Search/replace problems _do_ happen with the latter, because they tend
to contain lots of common strings, but I've never heard of any problems
with the former.

> How about adding checksums to taglines which are
> validated by tla? 
> (Something like: "tla-uuid: 2395f100-a41b-4af3-a310-c11ae7515d10
> ea0bc4fb85a0e892bd646ab07c6647ad" mhm crc32 or something even more
> simple should suffice)

If this approach were used, I think something a bit shorter would
suffice...

-Miles
-- 
Come now, if we were really planning to harm you, would we be waiting here, 
 beside the path, in the very darkest part of the forest?


_______________________________________________
Gnu-arch-users mailing list
Gnu-arch-users@gnu.org
http://lists.gnu.org/mailman/listinfo/gnu-arch-users

GNU arch home page:
http://savannah.gnu.org/projects/gnu-arch/