From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: Duy Nguyen <pclouds@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Prathamesh Chavan <pc44800@gmail.com>
Subject: Re: regression AGAIN in output of git-pull --rebase --recurse-submodules=yes --quiet
Date: Mon, 15 Apr 2019 16:40:30 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1904151635320.12614@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <robbat2-20190412T063235-859985527Z@orbis-terrarum.net>
Hi Robin,
On Fri, 12 Apr 2019, Robin H. Johnson wrote:
> Looking at git-rebase--preserve-merges.sh for this message, I think that
> should be a separate patch to make it respect --quiet.
Please note that `git rebase --preserve-merges` will be deprecated as of
the next Git version (see https://github.com/gitgitgadget/git/pull/158 for
details).
So I don't think it is worth the bother to fix that mode with respect to
--quiet.
Ciao,
Johannes
next prev parent reply other threads:[~2019-04-15 14:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-20 5:57 regression in output of git-pull --rebase --recurse-submodules=yes --quiet Robin H. Johnson
2018-01-25 19:08 ` [PATCH] builtin/pull: respect verbosity settings in submodules Stefan Beller
2018-01-25 19:18 ` Junio C Hamano
2019-04-10 6:41 ` regression AGAIN in output of git-pull --rebase --recurse-submodules=yes --quiet Robin H. Johnson
2019-04-10 11:18 ` Duy Nguyen
2019-04-12 7:08 ` Robin H. Johnson
2019-04-12 9:25 ` Duy Nguyen
2019-04-15 14:40 ` Johannes Schindelin [this message]
[not found] ` <CAODn77oL6sj5zvxgPGw=4TNqmnSeBq4=j2r2nx_51YHooECo7w@mail.gmail.com>
2019-04-16 7:48 ` Duy Nguyen
2019-04-12 10:08 ` [PATCH] submodule foreach: fix "<command> --quiet" not being respected Nguyễn Thái Ngọc Duy
2019-04-12 17:22 ` Robin H. Johnson
2019-04-15 2:59 ` Junio C Hamano
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=nycvar.QRO.7.76.6.1904151635320.12614@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=pc44800@gmail.com \
--cc=pclouds@gmail.com \
--cc=robbat2@gentoo.org \
/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).