Re: [PATCH] Support ent:relative_path
- From
- Dana How <danahow@gmail.com>
- Date
- May 4, 2007, 09:26 UTC
- Message-ID
- <56b7f5510705040226o14d55b6euda7df1da7ad9b08a@mail.gmail.com>
- In-Reply-To
- <81b0412b0705040217o54d1d028j6e768bdc3eb0bad0@mail.gmail.com>
On 5/4/07, Alex Riesen <raa.lkml@gmail.com> wrote:
Show 13 quoted lines
> > > > My preference is (2), (3) and then (1), but I do not have > > > > offhand a suggestion for a good metacharacter we could use. > > > > > > "./" :) > > Heh. Yes, that works in the current patch. > > > > I'm really starting to like the idea of introducing "=" > > as an alternative for ":" : > > "=" assumes relative paths, ":" assumes absolute (full) paths. > > That could be Junio's new metacharacter. > > Just keep in mind: "once introduced, you'll never be able to remove it". > And I don't share your feelings regarding the special character, for instance.
Indeed.
> I'd suggest to define a special character for _top_ level. Real pity > ":/" is taken.
We could use ://fullpath for top level, and :relpath for relative. Then "string" in :/string couldn't start with /, which shouldn't be a problem (right?). I've certainly seen double slashes before; perforce in fact uses them for the root of the repository (depot).
This all depends on deciding that :relpath should be the (incompatible) new default, and I'm not sure that's going to happen.
-- Dana L. How danahow@gmail.com +1 650 804 5991 cell