[Top][All Lists]

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

[Gnu-arch-users] Re: Re: Obsoleting abrowse

From: Mikhael Goikhman
Subject: [Gnu-arch-users] Re: Re: Obsoleting abrowse
Date: Mon, 1 Aug 2005 09:13:11 +0000
User-agent: Mutt/

On 01 Aug 2005 08:38:14 +0200, Matthieu MOY wrote:
> Mikhael Goikhman said:
> >
> > missing --categories and company,
> --categories and --branches are missing. Personnally, I think adding them
> to rbrowse would complexify the code (and the spec, since the current
> rbrowse never displays categories and branches individually, I don't know
> what the output of baz rbrowse --categories should be) a lot for very
> little benefit.

The format is the same as with --versions, just with less components.

Filtering by category and branch will always be useful. Otherwise why you
would want to use a/c-b-v namespace in the first place? It is only the
question whether such filtering should be done in individual frontends or
in baz. I think the second, like it is done now.

Anyway, I think abrowse should not be obsoleted for several months if you
remove the concept of category and branch in the new browse command.

> > full match rather than prefix match.
> If you mean "full match of category, branch, or version", this means the
> spec will have to change again with the future namespace change. I
> strongly prefer opting for the flat namespace now, and not having to
> change anything later.

If I have branches project--main, project--manpages, project--maintenance
then I can't think about a use case when I would want to receive all
versions (or revisions) given limit "project--ma" (I would use limit
"project" for this) or receive "maintenance" in "project--main" query.

I speak about non-regexp (exact) mode here. I don't care much about the
logic for regexp mode, that is non-exact by definition. you may define a
different behaviour of "project--ma", "project--ma.*" or ".*ma.*" for it.

> If you mean "full match of the version", this means the string match will
> match only one version, which is rather useless for rbrowse.

I don't agree that limit that is version is generally useless. However it
obviously should not be the only limit. The limit may be anything that
abrowse currently accepts, i.e. full archive, full category and so on.


reply via email to

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