Re: Another question about importing SVN with fast-import

From: David Frech <david@nimblemachines.com>
Date: Jul 20, 2007, 06:54 UTC
Message-ID: <7154c5c60707192354k7db677a6m4f8cbd474747ca92@mail.gmail.com>
In-Reply-To: <Pine.LNX.4.64.0707200646400.18125@beast.quantumfyre.co.uk>

On 7/19/07, Julian Phillips <julian@quantumfyre.co.uk> wrote:

Show 18 quoted lines

> On Fri, 20 Jul 2007, Shawn O. Pearce wrote:
>
> > It is possible.  I'm just not sure what the syntax for it should be.
> > Suggestions?  I really want to stay backwards compatible with the
> > current "C" command, so:
> >
> >       'C' SP commit SP path SP path
> >
> > is out because its ambiguous with the current meaning where the
> > second (destination) path can contain SP without being quoted by
> > the frontend.
>
> You could always make it part of the 'M' command?
>
> 'M' sp mode sp 'copy' sp path_str lf (ref_str | hexsha1 | sha1exp_str |
> idnum) SP path_str;
>
> Or just make it a new command, O (for other) or E (for existing) maybe? :S

Since we'll be referring to past commits via marks (with start with ":") how about this:

'C' SP srcpath:mark SP dstpath

In the case of making it a new command I can't think of any really compelling one letter names. ;-)

- David

Show 7 quoted lines

>
> --
> Julian
>
>   ---
> It is easier to change the specification to fit the program than vice versa.
>

-- 
If I have not seen farther, it is because I have stood in the
footsteps of giants.