non port: devel/git-absorb/distinfo |
SVNWeb
|
Number of commits found: 5 |
Sat, 19 Nov 2022
|
[ 15:21 Nuno Teixeira (eduardo) ] 24332da
devel/git-absorb: Adopt/Update to 0.6.9
ChangeLog: https://github.com/tummychow/git-absorb/compare/0.6.6...0.6.9
|
Mon, 22 Nov 2021
|
[ 19:54 Neel Chauhan (nc) Author: Evgeniy Khramtsov ] 4cde87e
devel/git-absorb: update to 0.6.6
Approved by: Greg V <greg@unrelenting.technology> (maintainer)
Changes: https://github.com/tummychow/git-absorb/compare/0.5.0..0.6.6
PR: 259681
|
Mon, 12 Aug 2019
|
[ 13:57 mat ]
Update to 0.5.0.
PR: 239778
Submitted by: mat
Reviewed by: maintainer
|
Thu, 28 Feb 2019
|
[ 18:47 jbeich ] (Only the first 10 of 70 ports in this commit are shown above. )
USES=cargo to update libc to 0.2.49 for Tier2
PR: 235063
Differential Revision: https://reviews.freebsd.org/D19309
|
Sat, 9 Feb 2019
|
[ 09:20 tcberner ]
New port: devel/git-absorb: Git command for automating fixup/autosquash commits
You have a feature branch with a few commits. Your teammate reviewed the branch
and pointed out a few bugs. You have fixes for the bugs, but you don't want to
shove them all into an opaque commit that says fixes, because you believe in
atomic commits. Instead of manually finding commit SHAs for git commit --fixup,
or running a manual interactive rebase, do this:
> git add $FILES_YOU_FIXED
> git absorb
> git rebase -i --autosquash master
git absorb will automatically identify which commits are safe to modify, and
which indexed changes belong to each of those commits. It will then write
fixup! commits for each of those changes. You can check its output manually if
you don't trust it, and then fold the fixups into your feature branch with
git's built-in autosquash functionality.
PR: 235436
Submitted by: Greg V <greg@unrelenting.technology>
|
Number of commits found: 5 |