3 ms·
Thanks, I knew about -committerdate but not that you can set it as default sort, super useful. A few notes... 1. git columns gets real confusing if you have mo
by chx 3y ago
Thanks, I knew about -committerdate but not that you can set it as default sort, super useful. A few notes...
1. git columns gets real confusing if you have more data than fits the screen and you need to scroll. Numbers would help...
2. git maintenance sounds great but since I do a lot of rebases and stuff, I am worried: does this lose loose objects faster than gc would? I see gc is disabled but it's not clear.
3. Regarding git blame a little known but super useful script is https://github.com/gnddev/git-blameall https://github.com/gnddev/git-blameall . (I mean, it's so little known I myself needed to port it to Python 3 and I am no Python developer by any stretch.)
- Forge36 3y ago2. It does not. It will pull data from the remote more often, and repack data. With GC turned off the data won't be deleted 3. Nice, I may have to try this
- masklinn 3y ago> git maintenance sounds great but since I do a lot of rebases and stuff, I am worried: does this lose loose objects faster than gc would? I see gc is disabled but it's not clear. “gc” is disabled for the scheduled maintenance. It’s enabled as task when running “maintenance run” explicitely. It would not collect loose objects faster than gc would, because it just runs gc.
- rendaw 3y agoIs there a way to do the reverse sort? A simple solution to branches going off screen seems to be have the latest branch last. That's what I do (although with a custom script).