On Thu, Nov 30, 2006 at 09:49:17AM +0100, Thomas Moschny wrote:
> On Thursday 30 November 2006 06:20, Nathaniel Smith wrote:
> > [...]
> > Also, to just remind everyone who hasn't been lurking for the last n
> > years, the other traditional argument for mtn commands being
> > unrestricted by default is that in this model both common use cases
> > are very natural:
> > current dir: mtn commit .
> > unrestricted: mtn commit
Presumably in this model you can still write
mtn commit ../../..
if you really want to.
> > but in the other model, one is not natural at all:
> > current dir: mtn commit
> > unrestricted: mtn commit ../../.. # or was that ../../../..? ../..?
>
> It is not that unnatural at all:
> unrestricted: pushd ../../.. ; mtn commit ; popd
>
> The concept of a current working directory is there for a reason, and
> programs
> should not simply ignore it. Of course we could always and everywhere work
> with absolute and complete paths, but *that's* not natural.
>
> - Thomas
>
>
> _______________________________________________
> Monotone-devel mailing list
> [email protected]
> http://lists.nongnu.org/mailman/listinfo/monotone-devel
_______________________________________________
Monotone-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/monotone-devel
