Just to make 100% sure, this means we should now commit all doc updates to both:
master 4.2-forward Please let us know if that's incorrect. Jessica T. ________________________________________ From: Animesh Chaturvedi [[email protected]] Sent: Wednesday, August 21, 2013 10:35 AM To: [email protected] Subject: RE: 4.2-forward branch created - Fwd: Git Push Summary I will also cherry-pick doc commits > -----Original Message----- > From: Radhika Puthiyetath [mailto:[email protected]] > Sent: Wednesday, August 21, 2013 9:55 AM > To: [email protected] > Subject: RE: 4.2-forward branch created - Fwd: Git Push Summary > > How about documentation ? Reviews are still going on. > > -Radhika > > -----Original Message----- > From: David Nalley [mailto:[email protected]] > Sent: Wednesday, August 21, 2013 9:28 PM > To: [email protected] > Subject: 4.2-forward branch created - Fwd: Git Push Summary > > Per our earlier discussion 4.2-forward branch is created - please don't > commit to 4.2, consider that frozen, and use 4.2-forward. If a patch > needs to make it in, please send a mail to the list to alert Animesh to > the fact and he can pull it over. > > --David > > > ---------- Forwarded message ---------- > From: <[email protected]> > Date: Wed, Aug 21, 2013 at 11:55 AM > Subject: Git Push Summary > To: [email protected] > > > Updated Branches: > refs/heads/4.2-forward [created] d019388bf
