libquicktime-transition now

[Fabian Greffrath]

Am Freitag, den 06.07.2007, 22:17 +0200 schrieb Loïc Minier:
>  It's manual, painful, and "loses" history; quite the opposite of git
>  where it's automatic, easy, and keeps history.  I recommend the second
>  technique instead which consist of replacing the unstable branch with
>  the experimental one (svn rm unstable/libquicktime; svn mv
>  experimental/libquicktime unstable), but only when you're done checking
>  you didn't leave anything behind.

OK, I think I got this.

So it is allright to manually merge the changelog from experimental and
the one from unstable into one new unstable changelog which remains
ordered by date? I think of the following:

libquicktime (2:1.0.0+debian-4) unstable
libquicktime (2:1.0.0+debian-3) experimental
libquicktime (2:1.0.0+debian-2) experimental
libquicktime (2:1.0.0+debian-1) experimental
libquicktime (2:0.9.7-5) unstable
libquicktime (2:0.9.7-4) unstable
libquicktime (2:0.9.7-3) unstable
libquicktime (2:0.9.7-2) unstable
libquicktime (2:0.9.10+debian-3) experimental
libquicktime (2:0.9.7-1) unstable
libquicktime (1:0.9.10+debian-2) unstable
libquicktime (1:0.9.10+debian-1) unstable
libquicktime (1:0.9.7-0.6) unstable
[...]

If you consider this a clean solution I will merge both changelogs,
remove the current unstable branch and copy the current experimental
branch over to unstable with the target set to unstable in the latest
changelog entry.