git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Thomas Gummerer <t.gummerer@gmail.com>
To: Karen Arutyunov <karen@codesynthesis.com>
Cc: git@vger.kernel.org
Subject: Re: git worktree add verbosity
Date: Sun, 5 Aug 2018 16:01:17 +0100	[thread overview]
Message-ID: <20180805150117.GG2734@hank.intra.tgummerer.com> (raw)
In-Reply-To: <02659385-334f-2b77-c9a8-ffea8e461b0b@codesynthesis.com>

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

  reply	other threads:[~2018-08-05 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-05 12:55 git worktree add verbosity Karen Arutyunov
2018-08-05 15:01 ` Thomas Gummerer [this message]
2018-08-05 18:37   ` Eric Sunshine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180805150117.GG2734@hank.intra.tgummerer.com \
    --to=t.gummerer@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=karen@codesynthesis.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).