From: Kristoffer Haugsbakk Date: Tue, 02 Jun 2026 07:54:02 GMT Subject: Re: [PATCH 2/2] builtin/init-db: deprecate alias for git-init(1) Message-ID: <455fc75a-444f-4760-a22f-54a2ec29618b@app.fastmail.com> In-Reply-To: On Tue, Jun 2, 2026, at 08:45, Patrick Steinhardt wrote: > On Tue, Jun 02, 2026 at 07:22:50AM +0900, Junio C Hamano wrote: >> "Kristoffer Haugsbakk" writes: >>>[snip] >> Or just leave it without deprecation. It does not cost much to keep >> "init-db", and because we expanded what "git database" means in >> later versions of Git since its invention, the name still makes >> sense. Thank Linus for not naming it "init-odb"---that might have >> been a valid excuse to rename it because it does not cover the ref >> database and config database and others. > > I wouldn't mind that outcome much, either. What triggered this series is > that I'm always annoyed that it's "builtin/init-db.c" instead of > "builtin/init.c", and the same for `cmd_init_db()`. But I intentionally > constructed the series in a way that the first commit can be picked > as-is, so that we can adjust our code to the modern world while not > doing the deprecation dance. > > So I'd be equally happy if we just drop the second commit in this > series. Could it be worthwhile to mark it as soft deprecated? In the sense that it is a legacy alias that is not planned for removal? What I think was mistake in topic jc/you-still-use-whatchanged was that git-whatchanged(1) was not explicitly marked as deprecated before that series, and then it started failing without a new `--i-still-use-this` flag. The doc before that said: New users are encouraged to use git-log(1) instead. The `whatchanged` command is essentially the same as git-log(1) but defaults to showing the raw format diff output and skipping merges. The command is primarily kept for historical reasons; fingers of many people who learned Git long before `git log` was invented by reading the Linux kernel mailing list are trained to type it. Reading between the lines, this looks like a soft deprecation. Then there were emails that said that there was no prior warning. And then someone replied to that saying that it had really been deprecated for over a decade because that was the intent.[1] But IMO just saying something to the effect of soft deprecated would have been better (before it got hard deprecated). Trying to simulate amnesia, I think just the word “init-db” looks slightly legacy, and the fact that the documentation just links to git-init(1) solidifies that. On the other hand git-stage(1) was introduced as a better name for “staging” files and that too just links to git-add(1). So you have two commands which just link to other commands, but one is definitely more deprecated than the other. † 1: But “trained fingers” reading the man page every other year on the off chance that there are new developments? That’s another question.