[HN Gopher] Bzg/woof: online monitor for mailing list based patc...
       ___________________________________________________________________
        
       Bzg/woof: online monitor for mailing list based patch workflow
        
       Author : todsacerdoti
       Score  : 26 points
       Date   : 2021-04-17 19:25 UTC (3 hours ago)
        
 (HTM) web link (github.com)
 (TXT) w3m dump (github.com)
        
       | davvid wrote:
       | The Git project was recently discussing[1] pain points in their
       | mailing list patch workflow. It's worth a read to get a feel for
       | issues projects encounter.
       | 
       | Another related project that's worth mentioning is
       | GitGitGadget[2][3], a tool that bridges the divide between Github
       | PRs and Git's mailing list patch workflow.
       | 
       | [1] https://public-
       | inbox.org/git/YHaIBvl6Mf7ztJB3@google.com/T/#...
       | 
       | [2] https://gitgitgadget.github.io/
       | 
       | [3] https://github.com/gitgitgadget/gitgitgadget
        
       | brian_herman wrote:
       | Cool any projects use this? What advantages does it have over git
       | or fossil?
        
       | lima wrote:
       | In somewhat related news, Gerrit has a new frontend and it's
       | awesome! Google has a couple of UX people working on it now and
       | it shows.
       | 
       | As a big fan of patch-based code review, I still can't stand
       | GitHub PRs. It's very annoying to stack GitHub PRs, so the
       | default is to create large PRs instead. This is sad, because
       | smaller units of review result in better code! Gerrit solves this
       | (and much more).
       | 
       | Example change on Gerrit (click on "Comments"):
       | 
       | https://gerrit-review.googlesource.com/c/gerrit/+/303182
       | 
       | Reasons to use Gerrit in spite of the learning curve:
       | 
       | - Ability to review commit messages (they're part of the
       | codebase!).
       | 
       | - Show diffs between different versions of a change, even across
       | rebases, with inline comments.
       | 
       | - Inline comments aren't lost on rebases and will be ported.
       | 
       | - Changes can be easily stacked.
       | 
       | - Select code snippets for inline comments, not just lines.
       | 
       | - It's really fast and there's keyboard shortcuts for everything.
       | 
       | - Rebase and cherry pick to release branches from the UI.
       | 
       | Some projects like Go, Cue or SQLAlchemy use custom tooling or
       | Copybara[1] to mirror PRs to Gerrit, which seems like the best of
       | both worlds - simple PR workflow for drive-by contributions,
       | patch workflow for core contributors who work with it all day.
       | 
       | [1]: https://github.com/google/copybara
        
       ___________________________________________________________________
       (page generated 2021-04-17 23:00 UTC)