[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-devel] Re: partial pull #2 - gaps instead of a single horizon
From: |
Thomas Moschny |
Subject: |
[Monotone-devel] Re: partial pull #2 - gaps instead of a single horizon |
Date: |
Wed, 27 Jun 2007 10:36:47 +0200 |
User-agent: |
KMail/1.9.6 |
Hi Derek,
Derek Scherger wrote:
> Thomas Moschny wrote:
> > Maybe. You didn't cite or answer my last question, which was: Why prefix
> > *all* paths in the db with a constant two-char string, when there never
> > will be a case where they are omitted for a reason?
>
> I don't understand your question, or the previous one. Perhaps one too
> many double negatives? Are you considering prefixing only *some* paths
> (i.e. just the root path)?
Sorry for being unclear ;) I am trying to rephrase.
If *every* string representing a path in the database started with "foo", that
prefix could also be omitted, because it would be redundant. If however only
some paths started with "foo" and the others did not, the prefix could
obviously not be omitted. That's all I wanted to say.
In your proposal, all paths in the db would start with './', and I was trying
to imagine (or asking you if you could imagine) an extension to your proposal
in which some paths don't have that prefix. If we can't find such a use case,
then there's no point in having that prefix *in the db* at all.
(Note that I'm not saying it wouldn't be useful in the GUI, i.e. presented to
or accepted from the user.)
Regards,
Thomas
pgpIukC4oiKWb.pgp
Description: PGP signature