[HN Gopher] Highlights from Git 2.37
___________________________________________________________________
Highlights from Git 2.37
Author : todsacerdoti
Score : 24 points
Date : 2022-06-27 18:02 UTC (5 hours ago)
(HTM) web link (github.blog)
(TXT) w3m dump (github.blog)
| tony wrote:
| Wow. I wasn't expecting anything like a filesystem monitor in
| git(1) itself.
|
| They post says Jeff Hostetler, the author of the patches, will
| make a blog post delving into it. So it's worth bookmarking that
| post and swinging back. It's bound to be an interesting one!
|
| Apparently git 2.16 had a fsmonitor hook for external filewatcher
| like watchman (it got passed me):
| https://github.com/git/git/commit/def4376711f607914bfb784f8d...
|
| This kind of change needs to be tailored to the platform, it says
| just Mac (FSEvents?) and Windows (ReadDirectoryChangesW?) for
| now. So can we expect Linux (inotify?) and BSD (kqueue*) in the
| future?
|
| Anyway, I hope this venture is fruitful. The premise of having
| cross-platform file watching without needing an extra application
| is delightful.
|
| Thank you Jeff!
|
| * I believe one area that may be tricky is kqueue, I believe it
| has limits in watching directories, needing a file descriptor for
| each file.
|
| P.S. I would like to drop a link to entr(1), a lightweight cross
| platform file watcher: https://eradman.com/entrproject/
| w-m wrote:
| The full release notes
| (https://github.com/git/git/blob/v2.37.0/Documentation/RelNot...)
| offer this highlight:
|
| "git -v" and "git -h" are now understood as "git --version" and
| "git --help".
|
| I wonder how many bikes were shed before that implementation
| could happen.
| stolee wrote:
| If you are curious, then you can find the discussion starting
| at v2 here:
| https://lore.kernel.org/git/20220330190956.21447-1-garrit@sl...
|
| This is a first time contributor getting a headlining feature
| at the top of the release notes!
| w-m wrote:
| Ah yes, thanks for linking that. So there was a discussion
| about a conflict with `--verbose` at least; whether to go for
| the upper case `-V` or completely drop the version flag from
| the patch. But then:
|
| "I do not care too deeply, and it is the most time efficient
| to just take the last patch as-is."
|
| Good lord, what a pragmatic maintainer! Burn them at the
| stakes!
| slaymaker1907 wrote:
| I'm disappointed they are deprecating the non-cone sparse-
| checkout style. Even if it messes with sparse indices, on Windows
| all my git operations are almost entirely dominated by individual
| file operations, not CPU or index operations.
| stolee wrote:
| Not deprecated. You can still use it. You need to manually opt-
| in using `git config core.sparseCheckoutCone false` since the
| default has switched.
___________________________________________________________________
(page generated 2022-06-27 23:02 UTC)