Re: [PATCH 2/4] fast-import: define a new option command

From: Shawn O. Pearce <spearce@spearce.org>
Date: Aug 13, 2009, 15:24 UTC
Message-ID: <20090813152419.GN1033@spearce.org>
In-Reply-To: <fabb9a1e0908130812s297ccfc6vd6b746daf1dcc69a@mail.gmail.com>

Sverre Rabbelier <srabbelier@gmail.com> wrote:

Show 7 quoted lines

> Actually I was thinking that the frontend should allow the user to override
> these options. Assuming it is, say, specifying a marks file, if the user
> wishes to change that, the frontend would probably need to know about the
> new location too.
> 
> So not only is it easier to implement, it makes sense from an ui
> perspective. No?

My point is, most of the options are about paths to local files.

If I export something from hg on machine A, then copy the fast-import stream to machine B, the marks file on B might not be in the same path. I might not even control machine A, maybe you emailed me that stream file. I may not be able to use an option on the source tool to alter the path.

Why shouldn't I be able to (easily) override the marks location locally, without resorting to stream editing?

Same with --force. Which probably now demands a counter option, --no-force. If you send me a stream with "option force\n" in the header, why can't I try to import it with "--no-force" first?

-- 
Shawn.