On Wed, Mar 13, 2019 at 4:05 AM Duy Nguyen <pclouds@xxxxxxxxx> wrote: > > On Tue, Mar 12, 2019 at 12:54 AM Elijah Newren <newren@xxxxxxxxx> wrote: > > > +--progress:: > > > +--no-progress:: > > > + Progress status is reported on the standard error stream > > > + by default when it is attached to a terminal, unless `--quiet` > > > + is specified. This flag enables progress reporting even if not > > > + attached to a terminal, regardless of `--quiet`. > > > > This again makes me curious what --quiet actually supresses; in the > > case of branch switching, are there any non-warning informational > > messages other than progress reports that are printed? > > One big thing git-checkout and git-switch will print when not --quiet > is "git diff --name-status" to highlight local changes since we allow > switching branches when the worktree is not clean. Should it be > mentioned in --quiet description? Nah, that all makes sense. It was more a curiosity (I tend to have a clean working tree most the time when switching branches, I guess; maybe I also filtered out messages I was used to seeing and couldn't remember seeing them) and also I had a small concern that perhaps this bit of documentation was relevant for one part of git-checkout and not the other, and thus shouldn't appear in both git-switch and git-restore. > We could also occasionally print advice, branch tracking info, and > one-liner summary like "Switched to (new) branch 'master'". Thanks for the explanations. This all makes sense. However, all these answers are specific to git-switch; perhaps the detailed explanation of --progress can be shorted for git-restore? Or does it too have reasons to print non-progress informational messages?
