RE: Locking trunk for commits to merge on load-store-redesign branch

[Pradeep Kamath <pr...@yahoo-inc.com>]

Hi,
  The process outlined below is now completed and the trunk is open for
commits which do not conflict with load-store-redesign branch.

Thanks,
Pradeep

-----Original Message-----
From: Pradeep Kamath [mailto:pradeepk@yahoo-inc.com] 
Sent: Monday, December 21, 2009 10:50 AM
To: pig-dev@hadoop.apache.org
Subject: Locking trunk for commits to merge on load-store-redesign
branch

Hi,

  PIG-1143 and PIG-1149 need special handling on the load-store-redesign
branch. PIG-1143 should not be applied to the branch since the code is
not applicable and for PIG-1149 there is a separate patch. I am
beginning a merge of load-store-redesign branch with current head of
trunk. These two patches will be committed to trunk once I complete the
merge and in the svn commit message for the merge on load-store-redesign
branch, I will record the revision after these two patches are
committed. This is so that the next time we merge from trunk to
load-store-redesign branch we merge from the point after these patches.
This mail is to let all committers know that they should hold off
commits till this process is done at which point I will send an "all
clear" email.

 

Thanks,

Pradeep