emlop
Git
emlop | Git | |
---|---|---|
15 | 287 | |
36 | 50,099 | |
- | 1.6% | |
9.0 | 10.0 | |
about 2 months ago | 2 days ago | |
Rust | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
emlop
-
20 Years of Gentoo
My oldest remaining emerge.log started in 2007. That desktop went thru some hardware upgrades, that you can spot them in the build time logs. Would love to see [emlop](https://github.com/vincentdephily/emlop) s -st -gy and emlop s -gy -e gcc from your machine.
-
emerge monitor written in C
Genlop is indeed slow, but qlop is comfortably fast, and emlop is even faster. I encourage you to check them out.
-
New to Gentoo. Is it safe to use - jN when emerging packages?
Happy to help. The size and number of packages is what's important, not whether you're installing or updating. I tend to only use emerge -j2 if I have 10 or more packages that can each build in a minute or less. You can always stop an emerge and restart it with emerge -rO -jN if you feel you made the wrong choice. You can use emlop p to get an estimate of how long the current emerge will take (current release is a bit outdated, I suggest installing from git: cargo install emlop --git https://github.com/vincentdephily/emlop).
-
What's the emerge command to have emlop p display the whole estimate?
Emlop is much faster than genlop, gives better estimates, has fewer bugs, and more features.
-
Compile time newbie help
That's a huge variation in merge times, things are usually a bit more predictable than this. They might just get progressively slower as new package versions get bigger.
-
dev-libs/icu and dev-libs/boost causing at least 2 hours of rebuilds
On the positive side, it inspired me to implement display of the current merge phase in emlop:
-
Portage doesn't show verbose output after using -q once.
emerge -rOp|emlop p can tell you how long the currently running merge will take, if it's something you've merged on that machine before. You could also suspend your laptop instead of shutting it down.
-
My turn to cry about compile times
emlop
-
Remind me why qtwebengine-bin does not exist?
While genlop works, I highly recommend emlop instead, as it is much faster (emerge -rOp | genlop -c is unusably slow) and featureful. The version in the GURU overlay is outdated at the moment, so either get it from the moltonel overlay or using cargo install emlop.
-
Announcing Pijul 1.0 beta, a Version Control System written in rust
There are a handful of commits that take especially long, for example cc8fa62c which updates many lines of a 5Mb test file. I've observed similar issues with the vim import. It seems that large diffs slow pijul down greatly, import time is not linear to diff size.
Git
- Git tracks itself. See it's first commit of itself
-
Resistance against London tube map commit history (a.k.a. git merge hell) (2015)
Look at any PR/patch series that got merged into the Git project. https://github.com/git/git/
Any random one. Because those that did not meet the minimum criteria for a well-crafted history would not have passed review.
- GitHub Git Mirror Down
- Four ways to solve the "Remote Origin Already Exists" error.
-
So You Think You Know Git – Git Tips and Tricks by Scott Chacon
Boy, I can't find this either (but also, the kernel mailing list is _really_ difficult to search). I really remember Linus saying something like "it's not a real SCM, but maybe someone could build one on top of it someday" or something like that, but I cannot figure out how to find that.
You _can_ see, though, that in his first README, he refers to what he's building as not a "real SCM":
https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23...
- Maintain-Git.txt
-
Git Commit Messages by Jeff King
Here is the direct link, as HN somehow removes the query string: https://github.com/git/git/commits?author=peff&since=2023-10...
- Git commit messages by Jeff King
- My favourite Git commit (2019)
-
Do we think of Git commits as diffs, snapshots, and/or histories?
I understand all that.
I'm saying, if you write a survey and one of the possible answers is "diff", but you don't clearly define what you mean by "diff", then don't be surprised if respondents use any reasonable definition that makes sense to them. Ask an ambiguous question, get a mishmash of answers.
The thing that Git uses for packfiles is called a "delta" by Git, but it's also reasonable to call it a "diff". After all, Git's delta algorithm is "greatly inspired by parts of LibXDiff from Davide Libenzi"[1]. Not LibXDelta but LibXDiff.
Yes, how Git stores blobs (using deltas) is orthogonal to how Git uses blobs. But while that orthogonality is useful for reasoning about Git, it's not wrong to think of a commit as the totality of what Git does, including that optimization. (Some people, when learning Git, stumble over the way it's described as storing full copies, think it's wasteful. For them to wrap their heads around Git, they have to understand that the optimization exists. Which makes sense because Git probably wouldn't be practical if it lacked that optimization.)
The reason I'm bringing all this up is, if you're trying to explain Git, which is what the original article is about, then it's very important to keep in mind that someone who is learning Git needs to know what you mean when you say "diff". Most people who already know Git would tend to gravitate toward the definition of "diff" that you're assuming (the thing that Git computes on the fly and never stores), but people who already know Git aren't the target audience when you're teaching Git.
---
[1] https://github.com/git/git/blob/master/diff-delta.c
What are some alternatives?
git-from-the-bottom-up - An introduction to the architecture and design of the Git content manager
scalar - Scalar: A set of tools and extensions for Git to allow very large monorepos to run on Git without a virtualization layer
emwa - Portage Log-Analysis
PineappleCAS - A generic computer algebra system targeted for the TI-84+ CE calculators
gentoo - [MIRROR] Official Gentoo ebuild repository
Subversion - Mirror of Apache Subversion
portage-utils - [MIRROR] Small and fast Portage helper tools written in C
vscode-gitlens - Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
scriptisto - A language-agnostic "shebang interpreter" that enables you to write scripts in compiled languages.
linux - Linux kernel source tree
gentooLTO - A Gentoo Portage configuration for building with -O3, Graphite, and LTO optimizations
chromebrew - Package manager for Chrome OS [Moved to: https://github.com/chromebrew/chromebrew]