How to exclude files from merging
Matt Mackall
mpm at selenic.com
Wed Nov 12 20:12:19 UTC 2008
On Tue, 2008-11-11 at 23:30 -0500, Douglas Philips wrote:
> On or about 2008 Nov 11, at 3:33 AM, Arne Babenhauserheide indited:
>
> > Am Montag 10 November 2008 21:26:15 schrieb Doug Philips:
> >>
> >> The question is: "How to make natural Mercurial workflows
> >> convenient enough to use so that the tedium of doing so does not
> >> interfere with the real task(s) at hand.."
>
> > Then the only code necessary in Mercurial to propagate repository
> > settings would be to allow for carrying the single setting which
> > states
> > which file is getting used as external config (maybe with the
> > (toggleable) restriction that the file must reside in the repository
> > and
> > be under version control).
>
> Thanks for the suggestions, but so long as it is philosophically
> opposed,
> any technology to do it is moot...
The philosophical issue is: we can't trust other users. Config files can
say things like "run 'rm -rf /' whenever you do an hg status". Thus,
it's not a good idea to put this under control of other users. Ever.
Any technology that doesn't address this very fundamental security issue
is indeed, as you say, moot. And I'm not very apologetic about it.
--
Mathematics is the supreme nostalgia of our time.
More information about the Mercurial
mailing list