The comments below are just about completeness -- I think it's a good
idea as proposed.
On Jul 19, 2007, at 3:47 AM, Blair Zajac wrote:
> You never pull an external from a subdirectory where you are, you
> always go up, so relative URLs will always start with a ..
Couldn't a user violate that assumption by planning to always check
out a his project using partial checkouts? This was already
addressed later in the thread (Blair wrote: " In that case, you could
use ./ to indicate a relative to current directory path."), unless
the implementation doesn't recognize and allow such.
> 2) Relative to the repository root
> There is the potential to refer to external repositories that are
> in the same level as the repository using the .. past the
> This relative URL will never break if you move the repository.
Unless it refers to "external repositories that are in the same level
as the repository using the .. past the repository root", right?
You'd then have to move repositories as a group and maintain their
> The relative URL to the current directory is easy: ../ You don't
> have externals to subdirectories, so these all start with ../.
Except given partial checkout, it is possible for externals to
subdirectories without contradiction. That case doesn't have to be
supported, but it is possible for some users to want it.
> My proposal is to introduce the ^ as the repository root character, as
> suggested by the regex anchor character, so ...
You've explained that it's likely unlikely in URLs and that Un*x
shells don't attribute special meaning to it, but nothing prevents it
from being the first character of a file/directory name (e.g. "(mkdir|
touch) ^hi"). That said, I think it's unlikely enough to be ignored
-- I don't recall ever seeing it used as the first character in a
Un*x file or directory name. I do like how intuitive it is to regex-
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Fri Jul 27 14:32:55 2007