managing multi-version development with mercurial

[Peter Arrenbrecht]

On Fri, Dec 4, 2009 at 7:21 PM, Alexander Schatten
<ml_alexanderschatten at gmx.at> wrote:
> Thank you very much for your suggestions. I think I generally got the idea with the dummy merges. however, this somehow sounds tricky to me.
>
> the solution I was planning was like this:
>
> If I need one (or few) changeset from some "older" version in a newer version, I thought, I export these changesets as patch and import the patch in the newer version.
>
> This seemed to me more transparent and straightforward as I just select the changesets I need in the other version(s).
>
> Is there some disadvantage with my idea that I don't see?

Don't know if you've seen it or not, but you might easily forget to
carry a fix in an older version forward to newer versions. I prefer
approaches where fixes get carried forward automatically and I have to
become active to prevent this, rather than the other way round.
-parren