Re: What's cooking in git.git (Aug 2011, #03; Thu, 11)
Hi Junio,
Junio C Hamano writes:
> I am envisioning that we would declare feature freeze after most of the
> topics that are in 'next' as of today graduate to 'master' for the next
> release, and keep the remainder cooking for the cycle after that. Hopefully
> that would happen around 24th.
> * rr/revert-cherry-pick-continue (2011-08-08) 18 commits
> [...]
> Will merge to "next".
If this won't graduate to 'next' before the 24th, I have plenty of
time to re-roll fixing all the issues that I've addressed in the
beginning of the new series. Depending on what you'd prefer, I can:
0. Do nothing. Get this series merged, and get the fresh series
merged as originally planned.
1. Squash the first few patches in the new series into this series and
post a re-roll. The new series will then be left with just two
commits.
2. Post a new series that combines both. I won't introduce any new
code, so no fresh review will be required. Since both the series have
been reviewed and tested independently, I don't see why this shouldn't
be possible.
Do let me know what you'd like. Thanks.
-- Ram
Ramkumar Ramachandra <artagnon@gmail.com>