Am 2017-05-10 um 23:48 schrieb Oleg Kalnichevski:
On Wed, 2017-05-10 at 23:25 +0200, Michael Osipov wrote:
...
But your answer is contrary to your previous statement -- cherry-
picking
shouldn't be a fuzz with two different repos. Can you explain
why?
My understanding is that cherry picking is not possible if remote
branches do not share the same commit history. If they do, they
might
as well be branches in the same repository.
Seems to be true. How about a patch from cherry-pick and a git apply?
I am not sure I understand what you mean by git apply.
Can we go back to what appears to be the only sticking point here?
It seems pretty clear that major release branches do not need to be in
different repos. Local clones per major release are perfectly
sufficient.
The question is whether or not people can live with HEADs of release
branches being volatile for a short period of time (not more than a few
days) until every active committer gets used to using dev branches for
building change sets?
To be more precise: do you want to do this only once or before every
release?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
