9 ms·
Highlights from Git 2.25
- richardwhiuk 7y ago> Sparse checkout management made easy Nothing about the following paragraphs of text sounds intuitive or easy...
- pjc50 7y agoIt's a lot of words to say "use a special checkout command then run `git sparse-checkout set A/B/C`"
- nerdponx 7y agoIt looks like a bunch of low-level machinery and primitives, which can be used to build more-intuitive tools.
- yegle 7y agoI think this is similar to Mercurial's narrow clone: https://www.mercurial-scm.org/wiki/NarrowClonePlan https://www.mercurial-scm.org/wiki/NarrowClonePlan This is very useful in a mono repo.
- jslabovitz 7y agoWhat’s up with Git’s peculiar usage of ‘learned’ in their release notes? For example: > Git learned the ability to execute a “partial” clone... > ..In Git 2.25, --format learned the verb l/L... I’ve never run across another piece of software that talked about itself this way. I’ve tried to research it in the past, to see if it’s part of some software engineering philosophy, but have always come up short. Anyone have any insight?
- rjsw 7y agoAt a guess - new command line options are created by a GAN.
- ilikejam 7y agoIt's not very common, but there's more than a few projects that use 'learned': https://www.google.com/search?q=changelog+%22learned%22 https://www.google.com/search?q=changelog+%22learned%22
- saagarjha 7y agoIt not uncommon to anthromorphize software.
- downerending 7y agoI remember several open source packages that used this idiom 15 or 20 years ago. It's probably a combination of a hat tip to the past, an inside joke, and the fact that the Git maintainer is not a native English speaker. Smile--I think it's meant to amuse.
- dragonwriter 7y ago> I’ve never run across another piece of software that talked about itself this way. Saying a piece of software “learned to” do something when it was programmed for a new feature is the same kind of anthropomorphism that leads one to talk about how a piece of software “talks about itself” when discussing project messaging, so it shouldn't seem that odd.
- cryptonector 7y agoWhat's the current state of Git and SHA-1?
- frakturfreund 7y agoThis: https://sidewalk.crustytoothpaste.net/tech/git/2020/01/11/sha-256-git https://sidewalk.crustytoothpaste.net/tech/git/2020/01/11/sh...
- cryptonector 7y agoThanks. Linus knew, damn it. He knew SHA-1 was obsolete.
- Mikhail_Edoshin 7y agoDid he? My impression was that they had SHA-1 from the start (maybe with a planned way to add another hashing) and only started to really switch gears when they got a real SHA-1 collision.
- wscott 7y agoThe post mentions merge.conflictStyle but one thing I would like to see git steal from BitKeeper is the unified diff conflict style. See the first example in this manpage: https://www.bitkeeper.org/man/smerge.html https://www.bitkeeper.org/man/smerge.html But we never managed to get that used much as you can infer by this help: -g Enable 'gca' output format that shows the local and remote files like a unified diff between the GCA and that file. This is the recommended output format, but not the default because it con- fuses people the first time they see it. You have to do more editing to resolve the conflict, but what changed is a lot more obvious.