3 ms·
This sounds not exiting at all. There's nothing wrong with releasing a bunch of small improvements, I just don't see why it's worth a HN front page entry, even
by perlgeek 11y ago
This sounds not exiting at all.
There's nothing wrong with releasing a bunch of small improvements, I just don't see why it's worth a HN front page entry, even as a regular git user.
- chimeracoder 11y agoMaybe not for you, but there are a number of things in here that could be relevant to people's workflows. For example: > The index file can be taught with "update-index --untracked-cache" to optionally remember already seen untracked files, in order to speed up "git status" in a working tree with tons of cruft. There are some companies out there that are using Git at such a scale that `git status` already takes as much as 20 or 30 seconds to complete. I'm not sure if this would speed up that particular issue, but it just goes to show that Git has a large range of use cases. Not all regular git users have the same needs.
- cdelsolar 11y ago.gitignore
- bicolao 11y agopart of the --untracked-cache feature is to reduce the cost of applying .gitignore patterns. When you have tons of files to check against some patterns, even strcmp() accumulates up.
- verbatim 11y agoI'm left to guess at what you mean by this exactly, but, .gitignore only helps with things that are agreed to be ignored by everyone. Files that are more specific to a particular developer or workflow don't always fit in there well. But, I'm not sure that's what this new capability helps with anyway. So, please elaborate.
- jrodl3r 11y agoobviously, you're not a golfer.
- hyperchase 11y ago> Files that are more specific to a particular developer or workflow don't always fit in there well. git config --global core.excludesfile ~/.gitignore
- jperras 11y agoThat's the beauty of a vote-based system: enough people thought it was interesting, so it made the front page.