To: John Meinel <tla@johnmeinel.com>
References: <20041025210724.GA19744@merconline.com>
	<200410272144.i9RLiYnd074868@xl2.seyza.com>
	<vpqoeinq0aw.fsf@ecrins.imag.fr> <418023CD.1000504@johnmeinel.com>
	<20041028023254.876A91436C5@comet.merconline.com>
	<418070AF.1070503@johnmeinel.com>
From: Matthieu Moy <Matthieu.Moy@imag.fr>
Mail-Followup-To: John Meinel <tla@johnmeinel.com>,
	James Blackwell <jblack@merconline.com>, gnu-arch-users@gnu.org
Date: Thu, 28 Oct 2004 09:19:33 +0200
In-Reply-To: <418070AF.1070503@johnmeinel.com> (John Meinel's message of
	"Wed, 27 Oct 2004 23:08:15 -0500")
Message-ID: <vpqoeincnsq.fsf@ecrins.imag.fr>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: gnu-arch-users@gnu.org, James Blackwell <jblack@merconline.com>
Subject: [Gnu-arch-users] Re: Potential flaw in patch-log pruning in	proposal
Precedence: list
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: 1551
Lines: 45
John Meinel <tla@johnmeinel.com> writes:

> James Blackwell wrote:
>
> Then you can also see what other revisions contributed to it. You
> don't know exactly which did what, but you do keep context sensitive,
> and you can locate it relative to just a couple packages.

Anyway, you can still "cat-archive-log" the full file if it gets
really necessary.

> I don't think =merged is going to be all the patch logs "cat"ed
> together. It's supposed to be just the fully qualified revision name.

That's what I meant.

> I believe that's what Matthieu stated. The sum of all the patch logs
> was > 7 MB for all of the logs, but for just the list of revisions it
> is only 120Kb.

Yes, but this is for xtla which is still a very small project. If you
want Arch to replace bitkeeper for the Linux kernel for example, you
have to multiply the digits by around 100 ...

Another option is to keep the name of individual patches on a
per-version basis. That is, instead of {arch}/=merged, you'd have one
{arch}/cat/branch/ver/=merged for each version merged in the tree.
Since the location of the file gives information about the fully
qualified version name, you can just keep the patchlevels in this
file, which makes it really small.

In a project with heavy use of microbranching, this will make a lot of
small files, though.

--
Matthieu


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