В Пнд, 20/09/2010 в 09:16 +0200, Michał Górny пишет:
> On Mon, 20 Sep 2010 09:44:38 +0400
> Peter Volkov wrote:
>
> > Another problem that there is no way to alter ChangeLog. Since
> > ChangeLogs are intended for users it's good idea to be able fix
> > typos / add credits there and thus it's impo
On Mon, 20 Sep 2010 09:44:38 +0400
Peter Volkov wrote:
> Another problem that there is no way to alter ChangeLog. Since
> ChangeLogs are intended for users it's good idea to be able fix
> typos / add credits there and thus it's impossible to generate them
> from git commit messages.
How about us
В Вск, 19/09/2010 в 16:17 +0100, Mike Auty пишет:
> It should be possible to still maintain this distinction, something like:
>
> "Version bump. Added feature foo.
> - --
> Feature foo required a complete rewrite of src_install."
>
> And then the ChangeLog generation can happen separately. The
On Sun, 19 Sep 2010 16:10:15 +0300
Petteri Räty wrote:
> One open question is what should repoman do if there is already a
> modification to the ChangeLog file.
I suggest reverting the ChangeLog modification. That's what my
sunrise-commit [1] does, and it works quite well.
On the other side, sh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It should be possible to still maintain this distinction, something like:
"Version bump. Added feature foo.
- --
Feature foo required a complete rewrite of src_install."
And then the ChangeLog generation can happen separately. The problem
with this
On 19-09-2010 16:10:15 +0300, Petteri Räty wrote:
> I assume many of us have wrapper scripts to automatically generate
> matching ChangeLog and CVS commit messages. When we eventually move to
> git the plan is for the ChangeLog to be automatically generated from
> git. To unify developer practices
On Sun, Sep 19, 2010 at 15:20, Krzysztof Pawlik wrote:
> On 09/19/10 15:10, Petteri Räty wrote:
>> I assume many of us have wrapper scripts to automatically generate
>> matching ChangeLog and CVS commit messages. When we eventually move to
>> git the plan is for the ChangeLog to be automatically g
On 09/19/10 15:10, Petteri Räty wrote:
> I assume many of us have wrapper scripts to automatically generate
> matching ChangeLog and CVS commit messages. When we eventually move to
> git the plan is for the ChangeLog to be automatically generated from
> git. To unify developer practices and to ease
I assume many of us have wrapper scripts to automatically generate
matching ChangeLog and CVS commit messages. When we eventually move to
git the plan is for the ChangeLog to be automatically generated from
git. To unify developer practices and to ease the transition to git it
has been proposed to
