Now that the essex docs have been cut, how should we handle back porting doc
fixes to the stable/essex branch?
I've been proposing doc changes to master and then, once the master is
approved, cherry-picking the commit and proposing to stable/essex . Is that
the way we should be doing it? If s
So far the git cherry-pick command has worked for me, so I think that is
the way to do it.
All I can think to do about the slippage is remind this group to request it
in their reviews of master. Any other ideas?
Anne
On Tue, May 8, 2012 at 12:44 PM, Lorin Hochstein
wrote:
> Now that the essex d
2 matches
Mail list logo