Re: Git's inconsistent command line options
- From
Barry Warsaw <barry@python.org>
- Date
- Aug 31, 2015, 14:25 UTC
- Message-ID
- <20150831102558.1514e5f7@anarchist.wooz.org>
- In-Reply-To
- <CACsJy8D3J6RhtPPtSvtWfOb8BapaX2-52M5_fE36psQPB_oQsQ@mail.gmail.com>
On Aug 31, 2015, at 05:10 PM, Duy Nguyen wrote:
Show 8 quoted lines
>I'm probably shot down for this. But could we go with a clean plate >and create a new command prefix (something like git-next, git2, or >gt...)? We could then redesign the entire UI without worrying about >backward compatibility. At some point we can start to deprecate "git" >and encourage to use the new command prefix only. Of course somebody >has to go over all the commands and options to propose some consistent >UI, then more discussions and coding so it could likely follow the >path of pack v4..
`git` itself could also be a thin wrapper which consulted a configuration variable to see which version of the ui to expose.
"All problems in computer science can be solved by another level of indirection"
Cheers, -Barry