given in bug #429649, and I have to
say that I don't find it at all persuasive as a reason to change the default
behavior of an established tool, and particularly not without announcing it.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer
On Mon, Sep 08, 2008 at 05:15:34PM +0200, Mohammed Adnène Trojette wrote:
On Wed, Sep 03, 2008, Steve Langasek wrote:
Now thanks to this behavior change, I'm apparently being unintentionally
vulgar in the main bug history of some bugs:
Well, I think bts is not to blame for the comment
for a release. Nothing in that implies that I
should have to edit and save changes in order for the tool to take the
action specified on the commandline, and I believe the common case is to
*not* edit changelog entries when using dch -r.
Please revert this change.
--
Steve Langasek
1fa018d9b4ae3ea3fd014b473953ab27dd0d972d Mon Sep 17 00:00:00 2001
From: Steve Langasek steve.langa...@canonical.com
Date: Fri, 3 Sep 2010 00:05:52 -0700
Subject: [PATCH] new script dep3changelog, which parses a DEP3 patch header and
feeds a suitable changelog entry to dch.
---
debian/changelog |4
be used for
native package builds, not for cross-package builds using multiarch. The
attach patch addresses this by causing mk-build-deps to always treat any
--arch argument as authoritative.
Cheers,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer
, it
ought not be standardized at all.
Now, given that git seems to be the only widespread VCS with theis problem, I
wouldn't object to codifying Vcs- fields for the others in the meantime; but
some people might find it equally unpalatable to specify fields for
everything except git.
--
Steve Langasek
