[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#935329: marked as done (ITP: git-revise -- handy git tool for doing efficient in-memory)

Your message dated Mon, 11 Nov 2019 11:00:16 +0000
with message-id <E1iU7Qe-000Eum-Je@fasolo.debian.org>
and subject line Bug#935329: fixed in git-revise 0.4.2-1
has caused the Debian Bug report #935329,
regarding ITP: git-revise -- handy git tool for doing efficient in-memory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
935329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935329
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist

* Package name    : git-revise
  Version         : 0.4.2
  Upstream Author : Nika Layzell
* URL             : https://github.com/mystor/git-revise
* License         : MIT/X?
  Programming Lang: Python
  Description     : handy git tool for doing efficient in-memory commit rebases & fixups

git revise is a git subcommand to efficiently update, split, and
rearrange commits. It is heavily inspired by git rebase, however it
tries to be more efficient and ergonomic for patch-stack oriented
workflows.

By default, git revise will apply staged changes to a target commit,
then update HEAD to point at the revised history. It also supports
splitting commits and rewording commit messages.

Unlike git rebase, git revise avoids modifying the working directory
or the index state, performing all merges in-memory and only writing
them when necessary. This allows it to be significantly faster on
large codebases and avoids unnecessarily invalidating builds.

%%

This is a nice shortcut over a bunch of complicated git commands that
would be very useful for novice and advanced users alike. It
completements git-rebase and similar, but is much simpler.

It seems like it's implementing its own git parsing engine in the
backend, so it doesn't have any dependencies, apart from git itself.

I do not plan on maintaining this and would be happy if someone else
stepped up. I mostly open this to document the package for other
developers.

--- End Message ---
--- Begin Message --- 
Source: git-revise
Source-Version: 0.4.2-1

We believe that the bug you reported is fixed in the latest version of
git-revise, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 935329@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Nicolas Schier <nicolas@fjasle.eu> (supplier of updated git-revise package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 26 Sep 2019 18:14:39 +0200
Source: git-revise
Binary: git-revise
Architecture: source all
Version: 0.4.2-1
Distribution: unstable
Urgency: medium
Maintainer: Nicolas Schier <nicolas@fjasle.eu>
Changed-By: Nicolas Schier <nicolas@fjasle.eu>
Description:
 git-revise - handy git tool for doing efficient in-memory commit rebases & fix
Closes: 935329
Changes:
 git-revise (0.4.2-1) unstable; urgency=medium
 .
   * Initial release (Closes: #935329)
   * Remove doc references to non-existing README.{source,Debian}
   * debian/control: wrap and sort control field values
   * debian/copyright: remove trailing whitespaces
   * Add git as dependency
   * Switch to debhelper-compat (= 12) build-dep
   * Mark FHS patch for upstream forwarding
   * Purge empty postinst,prerm templates
   * lintian: override false positive: todo.py is code not documentation
   * debian/control: remove Testsuite field, as autopkgtest is not yet used
Checksums-Sha1:
 85e58910815cc5943991c5d9dea99510fb9f7d7a 1561 git-revise_0.4.2-1.dsc
 c7703c3ce8065280bd396df0b5c32379c7c3afd9 31380 git-revise_0.4.2.orig.tar.gz
 4996e749e03739b2ac884a7c2a6ea801da004f6e 3100 git-revise_0.4.2-1.debian.tar.xz
 6e0ea9f732bfc779d44ff5625f3184b3d7778fc5 26016 git-revise_0.4.2-1_all.deb
 8e2abdaa73f8fef01c6e53df79c6636b6633f70e 5710 git-revise_0.4.2-1_amd64.buildinfo
Checksums-Sha256:
 1e8418c4b2f9d0e35985c7cc9f46af7632f03c68cdd71ad0c3d1d5174eb479c8 1561 git-revise_0.4.2-1.dsc
 217b1bb9a3b34d0c7e7544b516a9eed5bc061b9bafd3a97bc7edfd83ea54c0d6 31380 git-revise_0.4.2.orig.tar.gz
 3ce21df684e536e18cc10117bf4d4c8e094e7e2d83fb1834ca93285133641638 3100 git-revise_0.4.2-1.debian.tar.xz
 1aeecafd6516d6526eedb27784f1d8f54b98d71dcfee23a9c791916525631deb 26016 git-revise_0.4.2-1_all.deb
 80d0f0c9023c5b3c9390d4a564f53bfce7f67c992576890d0d697f075adc701a 5710 git-revise_0.4.2-1_amd64.buildinfo
Files:
 d62e0d212863796467fc1f430f28a6f1 1561 devel optional git-revise_0.4.2-1.dsc
 3982159006b21ed1ca3a35125540d7af 31380 devel optional git-revise_0.4.2.orig.tar.gz
 abffe04c68350f3a9f726b94038c0923 3100 devel optional git-revise_0.4.2-1.debian.tar.xz
 a95a8bedbd27c786e79f108648fe4a77 26016 devel optional git-revise_0.4.2-1_all.deb
 aa57177e5bec30e40931e16e30f1fdd6 5710 devel optional git-revise_0.4.2-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEexZCBNCWcjsBljWrPqHd3bJh2XsFAl2NE/wACgkQPqHd3bJh
2XtJ8wgAtiW1Rj/3rNKinCQNVC/QkBLn0ohT9Lsnbf7etBnGUicZDt8MrAWhGN9v
2Z43c64KWJuU3UXdZLDQIjufojvBJKVZB168TCav7uAjpG42qcTBaSMJq9ZqRyfI
coGizN2180r9dMJfO7R50zj9DtiTG2h+H2rxf6hkLc68orbA3kJVrYRF/hVk6U4X
NUhwt5oWZk8OHo97GNdj9bpDjp8GjXt5sT59xSs1ccINMUNzQgEkd8CGuI0Tat9A
p/JflSdxHVNm+U/kHsTT1VCGrWmVZ2GL5uNX3xQGymDSKPVHM+/h8z+YGHardseA
J8x2h2u0P+6WlVBO1Ueu3JSC6fM8HA==
=bh5Y
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: