From: Julian Phillips Date: Fri, 20 Jul 2007 05:50:31 GMT Subject: Re: Another question about importing SVN with fast-import Message-ID: In-Reply-To: <20070720051142.GO32566@spearce.org> On Fri, 20 Jul 2007, Shawn O. Pearce wrote: > David Frech wrote: >> On 7/16/07, Julian Phillips wrote: >>> Now the question. Shawn recently added C and R operations - almost as >>> soon as they were asked for too. However, how do you copy a file from a >>> particular revision? >> >> I have to second Julian's question. > > I'm getting to it. Maybe this weekend. Right now I have git-gui > work to finish, and that work is more important to me this week than > fast-import is. Not that fast-import isn't important to me either, > its just the way things are this week. No complaints from me - git-gui is one of the reasons I want to be able to use fast-import ;) >> The comment/question is: how different is this, really, from being >> able to specify a "from" line in a commit? In both cases I'm asking >> fast-import to reach into its memory (or the repo) and pull out a >> tree, and to add (some or all of it) to my current branch. Isn't the >> kind of generic C command that Julian and I are asking for the same >> thing, only instead of taking the whole tree (from the specified >> commit) it takes a single file or directory? > > 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 -- Julian --- It is easier to change the specification to fit the program than vice versa.