cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Prasanna Santhanam <...@apache.org>
Subject Re: [ACS42] Release Status Update: After Code Freeze Next Steps
Date Wed, 31 Jul 2013 05:03:51 GMT
On Tue, Jul 30, 2013 at 10:03:08PM +0000, Animesh Chaturvedi wrote:
> 
> 
> > -----Original Message-----
> > From: Alex Huang [mailto:Alex.Huang@citrix.com]
> > Sent: Tuesday, July 30, 2013 2:06 PM
> > To: dev@cloudstack.apache.org
> > Subject: RE: [ACS42] Release Status Update: After Code Freeze Next Steps
> > 
> > > The best type of commit for keeping things clean is a cherry-pick.
> > > Merging into the release branch is messy to track as the RM.
> > >
> > 
> > That should be a rule for release branches after code freeze.
> > 
> > --Alex
> [Animesh>] Thanks for clarifying, we will follow that for 4.2

Also can we do a git cherry-pick -x? It lists the original commit from
which the cherry was picked. Without it git branch --contains on a
commit id returns the wrong branch the commit was brought in from.

-- 
Prasanna.,

------------------------
Powered by BigRock.com


Mime
View raw message