Date: Mon, 27 Mar 2006 10:57:53 -0800 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-current@FreeBSD.org, Doug Barton <dougb@FreeBSD.org>, Ruslan Ermilov <ru@FreeBSD.org>, Steve Kargl <sgk@troutmask.apl.washington.edu> Subject: Re: mergemaster broken? Message-ID: <20060327185752.GG7001@funkthat.com> In-Reply-To: <20060327093402.H43553@fledge.watson.org> References: <20060320221741.GA13699@troutmask.apl.washington.edu> <20060320230009.GA55254@troutmask.apl.washington.edu> <20060320231604.GH83781@ip.net.ua> <20060320232746.GI83781@ip.net.ua> <20060320234006.GV35129@funkthat.com> <20060320234145.GB33003@troutmask.apl.washington.edu> <20060321064528.GD77849@ip.net.ua> <44206E9F.6020702@FreeBSD.org> <20060327093402.H43553@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Robert Watson wrote this message on Mon, Mar 27, 2006 at 09:38 +0000:
> So while I don't have opinions about the implementation details, I think
> what Ruslan is proposing is architecturally the right thing. How to handle
> the command line argument, I don't have an opinion, except that user
> surprise is bad, so a new argument with some compatibility and a warning is
> probably better than changing "-m".
Why not detect etc as the last component of -m and print a nice little
warning, and then remove /etc from the path? (or adding .. if we end
up with an empty path).. and after a year or so, remove the warning
and the compat code... I doubt people are doing something really crazy
like making foobarbaz a symlink to etc, and depending upon that.. If
they are, they get what the deserve...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060327185752.GG7001>