vcswatch reports that
this package seems to have a new changelog entry (version
0.6.0-1, distribution
UNRELEASED) and new commits
in its VCS. You should consider whether it's time to make
an upload.
Here are the relevant commit messages:
commit 8032603a2d2d68122a2ccbcf5935fffc7e0bfd72
Author: Nicolas Schier <nicolas@fjasle.eu>
Date: Mon Sep 7 21:49:41 2020 +0200
Satisfy pylint raise-missing-from warnings (patch)
Add 'from' to re-raise exceptions. Since version 2.6, pylint complains
about four raise-missing-from issues:
gitrevise/merge.py:207:12: W0707: Consider explicitly re-raising using the 'from' keyword (raise-missing-from)
gitrevise/merge.py:225:12: W0707: Consider explicitly re-raising using the 'from' keyword (raise-missing-from)
gitrevise/utils.py:73:8: W0707: Consider explicitly re-raising using the 'from' keyword (raise-missing-from)
gitrevise/utils.py:89:12: W0707: Consider explicitly re-raising using the 'from' keyword (raise-missing-from)
Simply adding the 'from' satisfies pylint.
Signed-off-by: Nicolas Schier <nicolas@fjasle.eu>
commit d69aac4551bb04c7aaebc26ea1e23daf1f642873
Author: Nicolas Schier <nicolas@fjasle.eu>
Date: Thu Dec 12 18:43:53 2019 +0100
Enable autopkgtest by using upstream tests
Signed-off-by: Nicolas Schier <nicolas@fjasle.eu>
commit e18e949809a15af490107e9a0c5b22ed873b7ef2
Author: Nicolas Schier <nicolas@fjasle.eu>
Date: Wed Jun 24 21:58:05 2020 +0200
Bump standards to 4.5.0 (no changes required)
Signed-off-by: Nicolas Schier <nicolas@fjasle.eu>
commit d8335cf87109d2a10a6d7fe1d978844d69e20cb4
Author: Nicolas Schier <nicolas@fjasle.eu>
Date: Fri Jun 12 13:00:15 2020 +0200
Remove superfluous FHS compliance patch (Closes: #944962)
Remove FSH compliance patch for git-revise.1 installation path. Change
is integrated in upstream.
Signed-off-by: Nicolas Schier <nicolas@fjasle.eu>
commit be9495084788e1e6f4e6a2f31bcbf218b71f5b4b
Merge: 6325fbe cbe8c16
Author: Nicolas Schier <nicolas@fjasle.eu>
Date: Fri Jun 12 12:58:11 2020 +0200
Merge tag 'v0.6.0' into debian/sid
Signed-off-by: Nicolas Schier <nicolas@fjasle.eu>
commit cbe8c162b85b0b57c3bd71c204ee091afe3d9336
Author: Nika Layzell <nika@thelayzells.com>
Date: Sun Jun 7 17:43:42 2020 -0400
v0.6.0
commit 80f2468f7ffb9f7fc0af8aa3382585484424b0dd
Author: Nika Layzell <nika@thelayzells.com>
Date: Sun Jun 7 17:35:31 2020 -0400
Test under python 3.8 (#67)
commit 758e31dc6410ee09febce0086912fda7267a52de
Author: Nika Layzell <nika@thelayzells.com>
Date: Sun Jun 7 17:15:46 2020 -0400
Update changelog
commit a5a531e42eb63abb65b16d48bffcb40456f796b3
Author: Robert Estelle <robertestelle@gmail.com>
Date: Sun Jun 7 14:09:24 2020 -0700
Respect `SEQUENCE_EDITOR` and `sequence.editor` vars (#60)
* Respect SEQUENCE_EDITOR/sequence.editor config
* Permit whitespace before comment characters in rebase-todo
Such comments are accepted by git-rebase-interactive and can be useful
in sequence editors. Otherwise a line starting with spaces and then a a
'#' would give the following error:
invalid value: step kind '#' must be one of: pick, fixup, squash, reword, cut, or index
commit 44390d1d91afcb0d3a5ea18e5dd562a02983d374
Author: Maksim Odnoletkov <odnoletkov@mail.ru>
Date: Sun May 17 00:36:36 2020 +0100
Support fixups with explicit hashes
Fixup commits usually use subject line of the target commit. But it is
also possible to specify the target commit's hash directly (or some
prefix of it):
fixup! faab8b162
This was added in Git in
https://github.com/git/git/commit/68d5d03bc49a073be3b0e14b22d30d70e7ae686d
and currently supported here:
https://github.com/git/git/blob/c44a4c650c66eb7b8d50c57fd4e1bff1add7bf77/sequencer.c#L2853-L2859
commit 837c779f17522fca0eaf4f8b59f4beefcef2496f
Author: Nika Layzell <nika@thelayzells.com>
Date: Sat May 16 13:00:13 2020 -0400
Correctly reorder fixup-of-fixup todos
Fixes #58
commit 114a08196382fa37386da52bf58678819bdb9544
Author: Nika Layzell <nika@thelayzells.com>
Date: Sat May 16 12:45:09 2020 -0400
Add support for git add's --patch flag
Fixes #61
commit 6d9d566ce45586f487257dba052d1b9cc2913b72
Author: Nika Layzell <nika@thelayzells.com>
Date: Sat May 16 12:33:35 2020 -0400
Add changenotes for recent changes
commit 59a14ca5df2a568c8530377684402f94279db8a1
Author: Ian McInerney <Ian.S.McInerney@ieee.org>
Date: Wed May 13 15:01:32 2020 +0100
Update man page install path to follow FSH
The Filesystem Hierarchy Standard wants man pages installed inside share/man, not man.
commit d6d558ce38dc94c10a8af0654e40ddb262fb9d01
Author: Robert Estelle <robertestelle@gmail.com>
Date: Sat May 2 13:58:11 2020 -0700
lint: Fix implicit binary f-string in __repr__
Original warning was:
gitrevise/odb.py:558: error: On Python 3 '{}'.format(b'abc') produces "b'abc'"; use !r if this is a desired behavior
commit faab8b162e5f7a662197ad473d464b16ddf4288e
Author: Robert Estelle <robertestelle@gmail.com>
Date: Sat May 2 13:57:27 2020 -0700
lint: Suppress non-top-level import warning
Unfortunately the module has a circular dependence, requiring this (or a
refactor).
commit d695bc8e753d6361a2492e7444f0424b2c965102
Author: Robert Estelle <robertestelle@gmail.com>
Date: Sat May 2 13:56:32 2020 -0700
lint: Fix "invalid-str" on enum value
Original error:
gitrevise/todo.py:17:4: E0307: __str__ does not return str (invalid-str-returned)
Although `.value` *is* a string, mypy (pylint?) doesn't figure that out.
commit 81163d8281da05d1aa30ecc8a0311d3623172c6b
Author: Robert Estelle <robertestelle@gmail.com>
Date: Sat May 2 13:55:28 2020 -0700
lint: Fix f-strings without interpolated variables
Original warning:
gitrevise/tui.py:115:14: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation)
gitrevise/tui.py:179:14: W1309: Using an f-string that does not have any interpolated variables (f-string-without-interpolation)
commit 83217837a7e5a3f2557aac719f52180855f8787a
Author: Robert Estelle <robertestelle@gmail.com>
Date: Sat May 2 13:54:46 2020 -0700
lint: Fix dangerous default value warning
Original warning was:
gitrevise/odb.py:713:4: w0102: dangerous default value os.environ (builtins.dict) as argument (dangerous-default-value)
commit 7db5da9a5d0828a426eb7aec1cae2c551f918bd9
Author: Robert Estelle <robertestelle@gmail.com>
Date: Sat May 2 13:53:27 2020 -0700
lint: Fix warnings on optional stdin/stdout members
The original errors were of the form:
gitrevise/odb.py:305: error: Item "None" of "Optional[IO[Any]]" has no attribute "write"
gitrevise/odb.py:306: error: Item "None" of "Optional[IO[Any]]" has no attribute "flush"
gitrevise/odb.py:309: error: Item "None" of "Optional[IO[Any]]" has no attribute "readline"
gitrevise/odb.py:325: error: Item "None" of "Optional[IO[Any]]" has no attribute "read"
commit dd50d19f793f304ec4e1261fdb81fc9d46397771
Author: Nika Layzell <nika@thelayzells.com>
Date: Sun Dec 22 12:25:21 2019 -0500
Ensure tests are run under tox-travis
commit 525de2f1fea85afe6c2694470bcf2e1e9530bee4
Author: Nika Layzell <nika@thelayzells.com>
Date: Thu Dec 19 12:15:48 2019 -0500
Minor documentation woring changes
commit e02e52fd1b1aee18015ebaca013a608e6780a539
Author: Thomas Otto <thomas.otto@pdv-fs.de>
Date: Tue Dec 10 17:46:04 2019 +0100
Update documentation and to-do list help
Deleted lines are no longer treated as index commands. Mention that
the number of lines must remain identical and that index commands must
come last. Adapt 'fixup' and 'squash' to mirror 'git rebase', so that
the 'fixup' help in the todo list mentions that the message is dropped.
Misc rephrasing.
commit 080d86ea652f90e98f8e9e5313d318505a567512
Author: Andreas Nordal <andreas_nordal_4@hotmail.com>
Date: Fri Nov 8 00:03:50 2019 +0100
(#45) Conflict editing: Say which commit failed to apply
commit 162ac90cba010a0f90f2290bf267d130466417d6
Author: Thomas Otto <thomas.otto@pdv-fs.de>
Date: Thu Nov 14 14:38:40 2019 +0100
Do not generate trailing whitespaces when writing comments
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/git-revise.png){kind=link}