On 1/16/07, C. Michael Pilato <cmpilato@collab.net> wrote:
> Daniel Berlin wrote:
> > On 1/16/07, Justin Erenkrantz <justin@erenkrantz.com> wrote:
> >> On 1/16/07, C. Michael Pilato <cmpilato@collab.net> 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?
This is a great way to end up accidentally submitting/committing
patches that contain things they shouldn't. It's hard to end up with
truly self-contained patches in GCC, and if i don't tag what i'm
working on with the changelist i'm working on it for, you can forget
why it's there.
Which isn't just bad when it happens, it makes you look bad, too.
:)
>
> > 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.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 17 04:48:27 2007