I wonder if Git provides a pluggable hashing mechanism as part of SHA2 migration.
I imagine stuff like this and SVN to Git mirroring to work nicely with identical hashes.
Extremely Linear Git History
11–20 of 366 posts
Re: Extremely Linear Git History
#12This is very silly.
but fun. Also might as well just mine bitcoins tbh...
Re: Extremely Linear Git History
#13Extremely Linear Git History...also known as SVN. Guess reinventing the wheel does get you to top HN.
You need to do it badly and wastefully.
Re: Extremely Linear Git History
#14I love linear git! Branches are very confusing for a nonempty set of people. For us, it is always clearer to work with explicit files in the main branch. You are implementing a new feature? Nice: just create a new file on the main branch and keep updating it until you add it to the tests, and later you call it from the main program. This system may break down on large teams, but when you are just a handful of grug-br…
This doesn't handle the reasonably common case very well where someone is working on changes which are constantly breaking the branch for everyone else. They should have their own branch and be frequently rebasing/merging so as to not disrupt others.
Also exploratory branches where any nonsense may go on (that may end up being merged, at least partially!). Also test/development vs. production branches! One may be broken, the production branch should ideally never be in a state that cannot be deployed.
That said, keep the branches limited and try to keep them 'linear' in the sense that you don't want to be merging between 100 different non-main branches in some byzantine nightmare. Perhaps encourage merges only to the development branch and then rebranching.
Re: Extremely Linear Git History
#15Re: Extremely Linear Git History
#16I mean.. this kind of breaks down if you have more than one person on the team
Re: Extremely Linear Git History
#17See also Lucky Commit [0], which uses various types of whitespace characters instead of a hash inside the commit, which makes it look more magical.
I wonder about performance, though. Why is the author's method slower than the package I linked?
Re: Extremely Linear Git History
#18Now, merge only the next-in-line hashes and the contributions to your repo can reach Cloud Scale™. Harness the ultimate power of distributed intelligent agents to create the future, backed by strong mathematical foundations and an ecosystem of innovative technologies. Just at your fingertips
Re: Extremely Linear Git History
#19This is horrible and I like it.
Re: Extremely Linear Git History
#20Sadly if you use commit signing it's unfeasibly slow to do this :(