How to Install and Uninstall git-revise.noarch Package on Fedora 36
Last updated: January 08,2025
1. Install "git-revise.noarch" package
Please follow the instructions below to install git-revise.noarch on Fedora 36
$
sudo dnf update
Copied
$
sudo dnf install
git-revise.noarch
Copied
2. Uninstall "git-revise.noarch" package
This guide covers the steps necessary to uninstall git-revise.noarch on Fedora 36:
$
sudo dnf remove
git-revise.noarch
Copied
$
sudo dnf autoremove
Copied
3. Information about the git-revise.noarch package on Fedora 36
Last metadata expiration check: 1:13:49 ago on Thu Sep 8 02:05:26 2022.
Available Packages
Name : git-revise
Version : 0.7.0
Release : 1.fc36
Architecture : noarch
Size : 15 k
Source : python-git-revise-0.7.0-1.fc36.src.rpm
Repository : updates
Summary : Efficiently update, split, and rearrange git commits
URL : https://github.com/mystor/git-revise
License : MIT
Description :
: 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.
Available Packages
Name : git-revise
Version : 0.7.0
Release : 1.fc36
Architecture : noarch
Size : 15 k
Source : python-git-revise-0.7.0-1.fc36.src.rpm
Repository : updates
Summary : Efficiently update, split, and rearrange git commits
URL : https://github.com/mystor/git-revise
License : MIT
Description :
: 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.