From: Thomas Gummerer <t.gummerer@gmail.com>
To: Karen Arutyunov <karen@codesynthesis.com>
Cc: git@vger.kernel.org
Subject: Re: git worktree add prints to stdout
Date: Sun, 5 Aug 2018 15:52:54 +0100 [thread overview]
Message-ID: <20180805145254.GF2734@hank.intra.tgummerer.com> (raw)
In-Reply-To: <631ae70d-9b5f-613d-5b6f-5064d548a894@codesynthesis.com>
On 08/05, Karen Arutyunov wrote:
> Hello,
>
> The 'git worktree add' command prints to both standard streams. So in the
> following example the first line is printed to stderr and the second to
> stdout.
git 2.18.0 should print both of those lines to stdout. This was done
to match where 'git reset --hard' prints the 'HEAD is now at...'
message. See also the thread at [1] where we did make that decision.
[1]: https://public-inbox.org/git/CAPig+cQ8VzDycUMo-QOexNDBgQGEGj2BPmPa-Y0vhGCt_brbhg@mail.gmail.com/
> $ git worktree add ../pub build2-control
> Preparing ../pub (identifier pub)
> HEAD is now at b03ea86 Update
>
> This looks like a bug, as, for example, the checkout command prints 'HEAD is
> now at...' message to stderr.
I think eventually it would be nice to write all those messages to
'stderr', as I think they do make more sense there. I said I may do
that at some point in [2], but never got around to it yet. If you
want to take a stab at it, feel free :)
[2]: https://public-inbox.org/git/xmqq604rzytx.fsf@gitster-ct.c.googlers.com/
> Best regards,
> Karen
next prev parent reply other threads:[~2018-08-05 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-05 13:01 git worktree add prints to stdout Karen Arutyunov
2018-08-05 14:52 ` Thomas Gummerer [this message]
2018-08-05 22:45 ` Jonathan Nieder
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=20180805145254.GF2734@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).