git-revise 0.4.2-1.1 source package in Ubuntu
Changelog
git-revise (0.4.2-1.1) unstable; urgency=medium * Non-maintainer upload. * No-change source-only upload to allow testing migration. -- Boyuan Yang <email address hidden> Wed, 04 Dec 2019 16:20:35 -0500
Upload details
- Uploaded by:
- Nicolas Schier
- Uploaded to:
- Sid
- Original maintainer:
- Nicolas Schier
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
| Series | Published | Component | Section |
|---|
Downloads
| File | Size | SHA-256 Checksum |
|---|---|---|
| git-revise_0.4.2-1.1.dsc | 1.9 KiB | 0e7a241273ecf5404e36759e1c4bd3ac0aecc9880f34a6facc87ddd986e5a0b0 |
| git-revise_0.4.2.orig.tar.gz | 30.6 KiB | 217b1bb9a3b34d0c7e7544b516a9eed5bc061b9bafd3a97bc7edfd83ea54c0d6 |
| git-revise_0.4.2-1.1.debian.tar.xz | 3.1 KiB | e11d3a628601e4054707c741584473f027b8d6fcc2ddd0d23809b8385261803d |
Available diffs
- diff from 0.4.2-1 to 0.4.2-1.1 (337 bytes)
No changes file available.
Binary packages built by this source
- git-revise: 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.
