Hi Danh, On Tue, 7 Apr 2020, Danh Doan wrote: > Adding this set of commands to Git gonna made Git over-complicated, > IMHO. Let me counter that by The Tale of the Green Button: while it is not completely historically accurate, it is a good illustration of focusing on What Matters Most: Once upon a time, Xerox built really nice copy machines that were very good and did a lot of useful things such as making one or more copies of one or more pages at a certain set of paper sizes with a certain set of paper criteria (heavy paper, shiny paper, double-sided copies) etc. And the tale goes: nobody used it. Then a usability expert came in, interviewed the users and figured out that it was too complicated to use. The result was the big green button with which you can make one copy using the standard paper size and the default paper. This set of commands that you are complaining about is intended to be that Big Green Button. Also, maybe we should not talk too loudly about "making" Git over-complicated. If you care to have a look at https://git-man-page-generator.lokaltog.net/ and find yourself being very much reminded of the current Git User Interface's complexity, you might agree that we should probably try to make _using_ Git less complicated. Even if it means adding new commands. Such as `git restore` and `git switch`. And, yes, like `git job-runner` (or whatever we end up calling it, I do agree with Junio that `git maintenance` is a nice name for its intended purpose). Don't just believe me. I invite you to interview the software engineers developing the Windows Operating System,. Or for that matter, _any_ software engineers working on projects substantially larger than git.git. Ciao, Dscho
