From: Jan Hudec <bulb@ucw.cz>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: David Frech <david@nimblemachines.com>,
Julian Phillips <julian@quantumfyre.co.uk>,
git@vger.kernel.org
Subject: Re: Another question about importing SVN with fast-import
Date: Mon, 23 Jul 2007 20:06:36 +0200 [thread overview]
Message-ID: <20070723180636.GA20174@efreet.light.src> (raw)
In-Reply-To: <20070720051142.GO32566@spearce.org>
[-- Attachment #1: Type: text/plain, Size: 887 bytes --]
On Fri, Jul 20, 2007 at 01:11:42 -0400, 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.
I'd suggest one of two variants:
1) 'M' SP <mode> SP <dataref> SP <path> LF
where <dataref> would be extended to understand the
{tag-id|commit-id|tree-id}:path notation git-ref-parse understands plus
mark:path where mark points to commit.
2) 'C' SP <dataref> SP <path> LF
where again <dataref> can be {tag-id|commit-id|tree-id|mark}:path -- or
just path which implies current head.
--
Jan 'Bulb' Hudec <bulb@ucw.cz>
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-07-23 18:07 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
2007-07-20 7:01 ` Julian Phillips
2007-07-20 7:16 ` David Frech
2007-07-23 18:06 ` Jan Hudec [this message]
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=20070723180636.GA20174@efreet.light.src \
--to=bulb@ucw.cz \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.