Message-ID: <418023CD.1000504@johnmeinel.com>
Date: Wed, 27 Oct 2004 17:40:13 -0500
From: John Meinel <tla@johnmeinel.com>
User-Agent: Mozilla Thunderbird 0.7.1 (X11/20040626)
MIME-Version: 1.0
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: Re: [Gnu-arch-users] Re: Potential flaw in patch-log pruning in
	proposal
References: <20041025210724.GA19744@merconline.com>	<200410272144.i9RLiYnd074868@xl2.seyza.com>
	<vpqoeinq0aw.fsf@ecrins.imag.fr>
In-Reply-To: <vpqoeinq0aw.fsf@ecrins.imag.fr>
Cc: gnu-arch-users@gnu.org, Thomas Lord <lord@emf.net>, jblack@merconline.com
Precedence: list
Content-Type: multipart/mixed; boundary="===============0293712807=="
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: 3234
Lines: 103
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--===============0293712807==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="------------enigA71F01E97C157E6003A6C1B8"

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigA71F01E97C157E6003A6C1B8
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Matthieu Moy wrote:
> Thomas Lord <lord@emf.net> writes:
> 
> 
>>So: how about we modify the process so that we maintain a file
>>
>>	./src/tla/=merged
>>
>>Each time a (log-pruned) version is merged into tla, it's version name
>>will be appended to that file.   No version name should appear twice
>>in that file.
> 
> 
> Wouldn't it be better to let (a future version of) tla maintain this
> file, and integrate it in the arch protocol instead of some user
> convention?
> 
> (I think you had another proposal on how to avoid log pruning, but I
> don't remember exactly what it was)
> 
> If I take the example of the Xtla project, on a freshly checked-out
> project, I get this:
> 
> $ du -sh
> 8.7M    .
> $ du -sh \{arch}/xtla/
> 7.4M    {arch}/xtla
> 
> So, the patch-log takes 85% of the disk space (7 times more than the
> source files !!). If I take only the list of merged patches in a file,
> it goes down to 120Kb, which is around 10% of the source size.
> 
> Another option would be to have a .tar.gz file of the patch-log. On
> Xtla, this makes a 400Kb compressed file, but I suppose this will make
> a big performance problem because to answer the question "is changeset
> X already merged?", tla would have to gunzip the whole file.
> 
> --
> Matthieu
> 

I think the idea that the patch name gets kept, but you can optionally 
keep the patch-log itself is a good idea. So the '{arch}/=merged' file 
would contain the equivalent of
tla logs --merges

Or possibly with the summaries as well. (This isn't as important, and 
might cause file size to go up again.)

Then when tla wants to check if a patch has already been merged, it can 
look for the patch-log, and secondly look for the entry in =merged.

It might be nicer if =merged was some sort of indexed file format, so 
that lookups could be faster, but greping even a 120K file doesn't seem 
very expensive.

John
=:->

--------------enigA71F01E97C157E6003A6C1B8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBgCPNJdeBCYSNAAMRAj9OAJ9f5Fg/CS2VDxe3jaFu1jCrtbsq7QCgoKoP
Ed0OdXXXUvYTgtT/M1YNlJY=
=dTQ8
-----END PGP SIGNATURE-----

--------------enigA71F01E97C157E6003A6C1B8--


--===============0293712807==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
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/
--===============0293712807==--