On 12 February 2010 04:04, John A Meinel <email address hidden> wrote:
> Note that mysql devs have also generally refused to set
> append_revisions_only on their trunk branch, as it was considered too
> disruptive for the development workflow that they are used to.
It seems like it would help them, but they may need other parts first.
At the moment people tend to merge trunk then to try to push to it.
This could be handled by the 'merge --reverse' idea, for which there
is a wishlist bug, letting them construct a new revision in which
their changes are the second parent and the trunk is the first. They
could then push into append_revisions_only.
Alternatively they could commit into a branch bound to trunk, but
perhaps there's some reason they can't do that now.
On 12 February 2010 04:04, John A Meinel <email address hidden> wrote: revisions_ only on their trunk branch, as it was considered too
> Note that mysql devs have also generally refused to set
> append_
> disruptive for the development workflow that they are used to.
It seems like it would help them, but they may need other parts first.
At the moment people tend to merge trunk then to try to push to it.
This could be handled by the 'merge --reverse' idea, for which there revisions_ only.
is a wishlist bug, letting them construct a new revision in which
their changes are the second parent and the trunk is the first. They
could then push into append_
Alternatively they could commit into a branch bound to trunk, but
perhaps there's some reason they can't do that now.
-- launchpad. net/~mbp/>
Martin <http://