[Top][All Lists]

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

Re: Feature request/ideas

From: Mark D. Baushke
Subject: Re: Feature request/ideas
Date: Wed, 02 Mar 2005 09:11:42 -0800

Hash: SHA1

Derek Price <address@hidden> writes:

> I just have one quibble, with your usage of
> ".root". The CVS manual and other sources use
> "root" to refer to what you are referring to as
> the "origin" of a branch. The logic being that a
> branch is always "rooted" in another branch, so
> the "root" refers to the revision actually on
> the parent branch.

Good point.

> I'm not sure what I would recommend in place of
> what you are calling the "root", but I would
> like to see ".root" refer to the revision on the
> parent branch.

I agree. That would be less confusing.

Maybe .first should indicate the first revision on
a branch?

'.first': Will always resolve to the first
revision on a branch ( will resolve
to [assuming that the *.1 version of
this branch has not been deleted]).

'.root': Will resolv to .first.prev, meaning the
predecessor of the first revision on the branch.

'.trunk': The most recently commited revision of
the mainline. If I have a file that has always
just been imported the file, and it is therefore
still using a 'branch 1.1.1;' in the RCS file, the
.trunk the most recently imported version
(possibly something like If an imported
file were modified and committed, the first
version might be 1.2 and .trunk would be 1.2 in
that case.

.trunk.first would usually be version 1.1 unless
someone had started that file initially on a
branch in which case .trunk.first might be 1.2
where 1.1 was a dead revision.

.trunk.first.prev would be "0" as a way of getting
a diff between /dev/null and whatever other
version was being compared.

The above is NOT what Frank has proposed, it is
just a possible renaming...

> The rest of your design looks great so far!

I Agree!

        -- Mark
Version: GnuPG v1.2.3 (FreeBSD)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]