From: Duy Nguyen Date: Mon, 31 Aug 2015 10:10:29 GMT Subject: Re: Git's inconsistent command line options Message-ID: In-Reply-To: On Wed, Aug 26, 2015 at 6:43 AM, Junio C Hamano wrote: > ... > > I do not see a good way to do such a safe transition with command > words approach, *unless* we are going to introduce new commands, > i.e. "git list-tag", "git create-tag", etc. 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.. -- Duy