Re: proposed X Strike Force commit/changelog policy
On Tue, Jun 10, 2003 at 02:20:45PM -0400, Joey Hess wrote:
> Branden Robinson wrote:
> > * When doing a commit that should be logged in the debian/changelog
> > file, edit the debian/changelog file before doing the commit and
> > commit the change to it along with the rest of your change set.
>
> As a point of interest, do you ever find yourself working on more than
> one thing at a time in the same checkout, and how do you juggle the
> debian/changelog changes then?
I tend to changelog everything I do as I do it, then when I'm about to
commit I copy the working changelog aside and trim debian/changelog down
so that the diff shows only one changeset. After I commit, I move the
working changelog back.
> > * Here's a new one that I myself didn't realize was important until this
> > morning: always include the name of each file being changed in your
> > commit log. This seems redundant until you realize that "svn log"
> > operations can be run on directories.
>
> Of course subversion knows what files that change touched. This sounds
> more like a deficiency of svn log; it should be able to list the files.
It can; use the -v option. I do tend to err towards verbose log messages
anyway, though.
> > What do you guys think?
>
> I'm not part of your team, but I have some interest in subversion and
> some of the same issues, so pardon me for weighing in..
Ditto.
Cheers,
--
Colin Watson [cjwatson@flatline.org.uk]
Reply to: