thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=release 2018-02-07T10:41:01Z 2018-02-07T10:41:01Z Daniel Kahn Gillmor dkg@fifthhorseman.net 2018-02-06T19:38:21Z urn:sha1:a9f1c7c294526afb2a2ac18003a654ea4c780b7b No one knows why this invocation is here. it does weird things during the build. If a developer really wants this behavior, they can specify it in their own ~/.gbp.conf Signed-off-by: Daniel Kahn Gillmor <dkg@fifthhorseman.net> 2011-12-15T04:20:11Z Jameson Graef Rollins jrollins@finestructure.net 2011-12-12T01:21:09Z urn:sha1:a06f7b6737de04b118af93cc247b052f6396fe0c Debian tags have been using '/', instead of '-' as a separator. 2010-04-16T17:00:11Z Carl Worth cworth@cworth.org 2010-04-16T17:00:11Z urn:sha1:7029c52ca7f0739d37f63f1659c6f60967d4fba3 David Bremner informs me that shoving everything from the notmuch "git log" into the debian/changelog is a bit excessive. Instead, we'll start manually updating this file, (which feels a bit redundant with NEWS, but perhaps makes us a better Debian-comunity member). 2010-04-16T16:32:46Z Carl Worth cworth@cworth.org 2010-04-16T15:49:09Z urn:sha1:2608bfe95f2c29ba568fa14904087882373971bc On Bdale Garbee's recommendation I'm switching from gitpkg, (which constructed a source tree but still required me to go run debuild), to git-buildpackage. I hadn't originally used git-buildpackage because it didn't seem to work without a configuration file, (where gitpkg was fine). Bdale was kind enough to point me to his fw/altos source at git.gag.com where I found an example gpb.conf file as well as a target in debian/rules to automatically update debian/changelog with the new version number.