Junio C Hamano <gitster@xxxxxxxxx> writes: > Dan McGee <dpmcgee@xxxxxxxxx> writes: > >> On 01/15/2008 10:23 PM, Junio C Hamano wrote: >>> I do not think it is unreasonable to add repo-config to feature >>> removal schedule in 1.5.4 release notes. Perhaps something like... >>> >>> + * "git repo-config", which was an old name for "git config" command, >>> + has been supported without being advertised for a long time. The >>> + next feature release will remove it. >>> + >> >> Seems fine to me. Does it need to be put in command-list.txt for the time being too, or what all is that file used for? Sorry I am not familiar. >> >> Something like: >> >> git-repo-config ancillarymanipulators deprecated > > Technically, you are right, but somehow it feels backwards. > > We stopped advertising the existence of the command in v1.5.0, > and adding it to the list now would mean we need to add a new > git-repo-config manual page that says "This is deprecated, use > git-config instead". This comment was wrong. We can keep the existing repo-config documentation that has deprecation notice, and add the above line to the list. Sorry about the confusion. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
