On Thu, Jun 3, 2010 at 06:23, Jonas Smedegaard <d...@jones.dk> wrote: > As a related not, there are several ways to keep track of packaging changes, > common ones being dch+dcommit and git+git-dch. > > Probably the most common one generally in Debian is to make your packaging > change, add a changelog entry using dch, and commit both the actual change > and the changelog update using dcommit. > > I prefer the alternative of making packaging changes, commit the actual > change, and only occationally (and at minimum right before a packaging > release) do a git-dch, maybe adjust the changelog file by hand (e.g. I > prefer to add a newline before bug-closures for improved readability), and > then commit the changelog update separately from the actual code changes. > > One thing I like about that git+git-dch approach is the code changes being > separate, which eases potential later reverts or cherry-picking across > branches.
Note that the team policy is to generate the changelog with git-dch at release time, precisely due to cherry-pick and revert ease. This is documented in the wiki page. -- Saludos, Felipe Sateler _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
