|
Number of commits found: 103 (showing only 3 on this page)
| Commit History - (may be incomplete: for full details, see links to repositories near top of page) |
| Commit | Credits | Log message |
0.3.0_2 28 Feb 2019 18:51:46
  |
jbeich  |
lang/rust: update to 1.33.0
- www/firefox temporarily loses SIMD in charset conversion, see
https://bugzilla.mozilla.org/show_bug.cgi?id=1521249
- Force rebuild all consumers to catch regressions early
Changes: https://blog.rust-lang.org/2019/02/28/Rust-1.33.0.html
Tested by: Mikael Urankar (aarch64, armv6, armv7, powerpc64), Piotr Kubaj
(powerpc64)
Approved by: rust (tobik)
Differential Revision: https://reviews.freebsd.org/D19354 |
0.3.0_1 28 Feb 2019 18:47:28
  |
jbeich  |
USES=cargo to update libc to 0.2.49 for Tier2
PR: 235063
Differential Revision: https://reviews.freebsd.org/D19309 |
0.3.0 09 Feb 2019 09:20:26
  |
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: 103 (showing only 3 on this page)
|