[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gnu-arch-users] Changelog and branches
From: |
Edouard Gomez |
Subject: |
[Gnu-arch-users] Changelog and branches |
Date: |
Fri, 12 Dec 2003 15:40:49 +0100 |
User-agent: |
Mutt/1.5.4i |
Hello,
This is just a convenience request.
I use a very basic development process:
merge
Mainline---mainline patches---+---------->
`---Future version branch---/
So when i tag the future branch, or i merge the 'future-version' branch
back to mainline, changelogs are filled by tens of new patches entries.
As changelog is only supposed to be a human representation of arch
maintained history, would it not be better to simplify its output in
such a case ?
I mean in my case i get:
new patches:
address@hidden/xvidcore--devapi4--1.0--base-0
address@hidden/xvidcore--devapi4--1.0--patch-1
...
address@hidden/xvidcore--devapi4--1.0--patch-80
It could be turned into something looking a bit like abrowse
archive/category output:
new patches:
address@hidden/xvidcore--devapi4--1.0
base-0 .. patch-80
For sparse merging, the output would just aggregate the sparse patch
ranges (eg: patch-50 .. patch-52\npatch-64\n.....). The output would
still be more compact than the current output.
If this request makes sense to other people, i'll fill a bug report to
savanah project.
--
Edouard Gomez
- [Gnu-arch-users] Changelog and branches,
Edouard Gomez <=
- [Gnu-arch-users] Re: Changelog and branches, Stig Brautaset, 2003/12/12
- Re: [Gnu-arch-users] Re: Changelog and branches, David Allouche, 2003/12/12
- Re: [Gnu-arch-users] Re: Changelog and branches, Samium Gromoff, 2003/12/15
- Re: [Gnu-arch-users] Re: Changelog and branches, Jason McCarty, 2003/12/15
- Re: [Gnu-arch-users] Re: Changelog and branches, Samium Gromoff, 2003/12/15
- Re: [Gnu-arch-users] Re: Changelog and branches, Tom Lord, 2003/12/15
- Re: [Gnu-arch-users] Re: Changelog and branches, David Allouche, 2003/12/17