Hi,
On Tue, Oct 22, 2019 at 07:35:55AM -0400, Sam Hartman wrote:
> I agree that better handling of things like debian/changelog is
> something we should focus effort on.
>
> I think we can either do something gbp dch like, possibly allowing
> commits to annotate whether and to what extent they sh
Hi,
On Tue, Oct 22, 2019 at 04:47:53AM +0200, Bastian Blank wrote:
> In Debian most people prefer to have changelog entries with all changes,
> so changes always contain a modification to debian/changelog.
It's worse than that: changelogs are supposed to contain the linear history
of the branch
On Mon, Oct 21, 2019 at 11:06 PM Bastian Blank wrote:
> There is "gbp dch", which ignores merge commits (so no really good for
> merge requests), but I don't consider it to have enough control over the
> content of the changelog.
Just set your merge settings per project to fast-forward.
Thanks,
On Tue, 22 Oct 2019 07:35:55 -0400, Sam Hartman wrote:
> Or some code that knows how to merge changelogs
dpkg-mergechangelogs(1) is a nice helper for some of the merge
situations.
Cheers,
gregor
--
.''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org
: :' : OpenPGP
I agree that better handling of things like debian/changelog is
something we should focus effort on.
I think we can either do something gbp dch like, possibly allowing
commits to annotate whether and to what extent they should be included
in changelog.
Or some code that knows how to merge chang
Hi Bastian,
Full disclaimer: I probably don't contribute often enough inside
Debian to be a reference on it but thinking about it I'm wondering if
it wouldn't be easier to do it another way.
On Mon, Oct 21, 2019 at 8:06 PM Bastian Blank wrote:
> There is "gbp dch", which ignores merge commits (s
6 matches
Mail list logo
