From: Lucas Seiki Oshiro Date: Wed, 25 Feb 2026 16:08:50 GMT Subject: Re: [RFC RFC PATCH] builtin/repo.c: change info default behavior to show all fields Message-ID: In-Reply-To: <20260225153132.7387-1-valusoutrik@gmail.com> Hi! > Yup, after reading it I did realise how pointless my suggestion was. I wouldn't say it was pointless, since you identified something that you thought that could be improved, found the code to be changed and sent a patch proposing your change. The default behaviour of git-repo-info with no arguments was not a complete consensus at the first place, some people thought it needed to return all the values, and some thought that no value should be returned. Although in this case I was on the "winner" side (I'm using quotes because I don't think this is a competition), many changes that I did were rejected at first place, and I couldn't see at first what were the problems with them, which I couldn't see only after the reviewing process. The reviewing process is very strict, and it couldn't be different, since Git is used by more than 90% of the developers [2]. Finally, I must say that most things that I think that should do falls under three situations: 1. Git already does that, and I didn't know 2. It was already discussed, and people agreed that Git shouldn't do it 3. It's not possible to do that In your case, it falls in the situation 2 and the discussion, being already discussed [3]. But I understand that it can be frustrating sometimes, and hope you don't feel discouraged in contributing to Git. [1] 20250610152117.14826-1-lucasseikioshiro@gmail.com [2] https://survey.stackoverflow.co/2022/#version-control-version-control-system-prof [3] 20250915223618.13093-1-lucasseikioshiro@gmail.com