git worktree add verbosity

Hello,

We are using git for automation in our build2 project.

What's quite inconvenient is that the 'git worktree add' command prints 
some output by default and there is no way to suppress it, as it 
normally can be achieved with the --quiet option for the most of git 
commands.

Could you add support for the --quiet option for the worktree command?

Best regards,
Karen

On 08/05, Karen Arutyunov wrote:

Hello,

We are using git for automation in our build2 project.

What's quite inconvenient is that the 'git worktree add' command prints some
output by default and there is no way to suppress it, as it normally can be
achieved with the --quiet option for the most of git commands.

Could you add support for the --quiet option for the worktree command?

I think a '--quiet' option would be nice to have.  I wouldn't need it
much personally, so I'm probably not going to work on it, but it would
be great if you could work on that.  The best place to get started
with contributing is to read Documentation/SubmittingPatches document.
The CONTRIBUTING.md in the git-for-windows repository [1] may also
have some helpful pointers.  Some of it is windows specific, but a lot
of it is generally applicable.

I'm happy to help reviewing these patches, and give more pointers to
help you get started.  Another useful resource is the #git-devel IRC
channel on Freenode, where you may be able to get some help (may need
some patience though :))

[1]: https://github.com/git-for-windows/git/blob/master/CONTRIBUTING.md

Best regards,
Karen

On Sun, Aug 5, 2018 at 11:01 AM Thomas Gummerer [off-list ref] wrote:

On 08/05, Karen Arutyunov wrote:

quoted

What's quite inconvenient is that the 'git worktree add' command prints some
output by default and there is no way to suppress it, as it normally can be
achieved with the --quiet option for the most of git commands.

Could you add support for the --quiet option for the worktree command?

I think a '--quiet' option would be nice to have. [...]

Indeed, omission of a --quiet flag was not an oversight, but rather
considered an optional feature "awaiting demand"[1]. Apparently, there
is now demand for it.

[1]: https://public-inbox.org/git/1436203860-846-12-git-send-email-sunshine@sunshineco.com/