Hi Jonathan, On Mon, May 10, 2010 at 2:59 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote: > Since the conflict resolution is trivial, I agree. When there is an > actual dependency between patches, I think there is nothing wrong > with basing one patch on another; as long as you make it clear > what your patch applies to, humans and Junio’s scripts can cope with > the task of applying one series on top of the topic branch for > another. Okay, got it. > Re your skeleton code, it looks reasonable to me. I could nitpick the > names of the import_handler() and export_handler() functions and the > needless use of do ... while, but I will refrain. :) Yeah, I suppose that can wait for a couple of weeks- atleast until I have something minimally working :) > Much more importantly, there is something to play with now. On that > note, is David’s code out there somewhere for people to fool around > with? At this point, I am not interested in a stable interface or > permanent history, just a way to try out the code and start to get > used to it. Yes. You can see it on David's GitHub [1] and my fork [2]. I send patches to David by email, so both should be in sync. -- Ram [1] http://github.com/barrbrain/svn-dump-fast-export.git [2] http://github.com/artagnon/svn-dump-fast-export.git -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html