We can probably just block anything thats more than a week old; you
shouldn't need to manually check through each commit IMO. We usually merge
fixes immediately to the 1-x branch anyways. Also, we can always just
unblock revisions that we need in the future.
On Fri, Jan 16, 2009 at 12:41 AM, Wille
Hold on, you said its a huge piece of work... You know you can just pass in
the big list of revisions to the block command right? Something like
svnmerge.py block -r
709613,709635,711586,711642,711677,711750,711926,712093,712133,712165..
Maybe I'm just not understanding due to baby i
Hi Jon,
If you want to go through the version's log to make sure it is not the
version which we want to merge into camel-1.x branch. That will be a
huge work.
But if we just make assumption that all the patch for camel-1.x are
merged, the blocking thing could be much easy.
Anyway, it's good to h
On Tue, Jan 20, 2009 at 6:19 AM, Willem Jiang wrote:
> Hi Jon,
>
> If you want to go through the version's log to make sure it is not the
> version which we want to merge into camel-1.x branch. That will be a
> huge work.
Yeah, makes sense now.
>
>
> But if we just make assumption that all the
