Daniel Berlin wrote:
> On 1/16/07, Justin Erenkrantz <firstname.lastname@example.org> wrote:
>> On 1/16/07, C. Michael Pilato <email@example.com> wrote:
>> > written, it didn't actually solve any interesting problem that didn't
>> > already have a simple (albeit mildly annoying) workaround, and that the
>> > feature and its maintenance were, by and large, unjustifiable baggage.
>> What's the simple workaround? It's a very helpful feature if you have
>> multiple patches in your tree. Or, am I misunderstanding something?
>> -- justin
> Yeah, i don't get the "mildly annoying" workaround either.
svn diff + patch, give or take any property edits? I constantly have
multiple patches-in-progress in my working copies, too, but a) manage
them just fine with 'svn diff' and patch, and b) always feel kinda
naughty, like I'm violating a best practice, for not keeping my tree
limited to a single changeset at a time.
> I use it to work on multiple changes in my gcc trees and manage them
> all the time using this.
Well, I'm glad to hear that somebody is using it. That's the kind of
input I was hoping to get from this query.
C. Michael Pilato <firstname.lastname@example.org>
CollabNet <> www.collab.net <> Distributed Development On Demand
Received on Tue Jan 16 21:24:34 2007