Re: svn commit: r33855 - in branches/tree-conflicts-notify/subversion: include libsvn_client libsvn_wc svn tests/cmdline tests/cmdline/svntest

Greg Stein wrote on Thu, 23 Oct 2008 at 04:09 -0700:
> > Is it the question of being easily able to know what to review that's
> > most important here?
>
> Yes. And to that point, let me formally suggest a /patches/ directory,
> as a sibling to /branches/. We can put developer-work in there, and we
> can also drop third-party patches in there, too, pending
> review/tweaking/application (rather than attach them to the issue
> tracker, for example).
>
> Thoughts?
>

Throwing fell-through-the-cracks third-party patches in the repository is
reasonable, and (with my patch manager hat on) not much effort. Throwing
*all* third-party patches to temporary branches in the repository before
applying them seems to me to introduce unnecessary overhead (but I'm sure
you weren't suggesting that :) ).

Daniel

> Cheers,
> -g

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-10-23 15:00:41 CEST