From: "David Frech" <david@nimblemachines.com>
To: "Julian Phillips" <julian@quantumfyre.co.uk>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: Another question about importing SVN with fast-import
Date: Thu, 19 Jul 2007 23:54:30 -0700 [thread overview]
Message-ID: <7154c5c60707192354k7db677a6m4f8cbd474747ca92@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707200646400.18125@beast.quantumfyre.co.uk>
On 7/19/07, Julian Phillips <julian@quantumfyre.co.uk> wrote:
> 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
>
> --
> 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.
next prev parent reply other threads:[~2007-07-20 6:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-16 21:11 Another question about importing SVN with fast-import Julian Phillips
2007-07-17 3:38 ` Shawn O. Pearce
2007-08-06 13:13 ` Julian Phillips
2007-08-07 1:08 ` Shawn O. Pearce
2007-07-19 7:09 ` David Frech
2007-07-20 5:11 ` Shawn O. Pearce
2007-07-20 5:50 ` Julian Phillips
2007-07-20 6:54 ` David Frech [this message]
2007-07-20 7:01 ` Julian Phillips
2007-07-20 7:16 ` David Frech
2007-07-23 18:06 ` Jan Hudec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7154c5c60707192354k7db677a6m4f8cbd474747ca92@mail.gmail.com \
--to=david@nimblemachines.com \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).