Re: [SCM] zita-convolver packaging branch, master, updated. debian/1.0.0-2-14-g2f3799f

[Jaromír Mikeš]

> Od: Felipe Sateler <fsateler at gmail.com>

> ----------------------------------------
JM> On Wed, 2009-12-02 at 02:40 +0000, mira-guest at users.alioth.debian.org
JM> wrote:
JM> > The following commit has been merged in the master branch:
JM> > commit be884194e2d5262f3cf76d6394ae31ae7e2cfb98
JM> > Author: Jaromír Mikeš <mira.mikes at seznam.cz>
JM> > Date:   Wed Dec 2 03:29:45 2009 +0100
JM> >     Edited control file

FS> Please use more meaningful commit messages. The idea of commit messages
FS> is to note what is not obvious with a simple diff (and friends). 

FS> In this particular case, you mixed the updating of standards-version,
FS> soname change in the library, and descriptions. While it is not really
FS> difficult to discern (in this commit) what happened, it is better to
FS> look at one change at a time. Please do that when you keep updating your
FS> packages.

Hi,

I understand you request...
my usual work-flow for upgrading source is :
- get build package again
- get package lintian clean again
- than make commits for all changed files
this avoid me from from too many commits if I do something wrong. 
And I usually do ;)
Too many commit ( do something undo something) in git repo make repo ugly IMO.

Is there way to split commits for multi-edited file?

regards

mira