On 04 Aug 2005 15:24:43 -0500, kfogel@collab.net <kfogel@collab.net> wrote:
> Now I'm more confused :-). Let me try restating what I think the goal
> is, then you tell me if I'm on the right track.
>
> The p-b-i branch is currently in a good, mergeable state right now,
> and you don't want to interfere with that, because you know Ben Reser
> is about to review it. But you also don't want to stop further
> development. So, you want one branch for Ben to review, and another
> on which you can keep working without interruption.
Exactly.
> If this is the plan, let's use clear names to indicate it:
>
> 1. Copy p-b-i to p-b-i-interim-for-review
>
> 2. Continue working on p-b-i as before.
>
> 3. Supply Ben Reser with the exact commands he'll need to review
> p-b-i-interim-for-review, to save him time.
>
> 4. Any tweaks you make to p-b-i-i-f-r, make to p-b-i as well. If
> one absorbs any trunk changes or bugfixes, the other must absorb
> them as well, and vice versa, so that the difference between the
> two branches is always simply the further work done on the p-b-i
> branch.
>
> 5. If Ben wants to review p-b-i-i-f-r as well, he can, but it might
> be more efficient for him to just do p-b-i (or a subset thereof)
> and then we'll see where things stand.
Yes, this is exactly right.
I've already got a few tweaks I'd like to make to "p-b-i-i-f-r", but I
don't want to make them dependent on my "abstract bindings work". The
two need to be independent, so that we can merge my bugfixes to trunk
without merging the experimental abstract bindings.
Is "python-memory-management" a good name? That describes what's on
the branch -- the memory management code, plus any fixes that need to
be made.
Cheers,
David
>
> B-e-s-t,
> -K-a-r-l
>
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Aug 4 23:29:43 2005