From: Stefan Beller <sbeller@google.com>
To: leif.middelschulte@gmail.com
Cc: git@vger.kernel.org, gitster@pobox.com,
sandals@crustytoothpaste.ath.cx, sbeller@google.com
Subject: [PATCH 0/2] Submodule merging: i18n, verbosity
Date: Thu, 10 May 2018 14:19:15 -0700 [thread overview]
Message-ID: <20180510211917.138518-1-sbeller@google.com> (raw)
In-Reply-To: <CANw0+A_T5zDUUWznYBe0m9fkSODPnfQaK1yJKPPawHTxi9+9BQ@mail.gmail.com>
Leif wrote:
> Sure, let me know what to use instead and I’ll update and resubmit the patch.
> Sure, but `MERGE_WARNING` prefixes all the messages with "Failed to
> merge submodule“.
I thought about replying and coming up with good reasons, but I wrote some
patches instead.
They can also be found at https://github.com/stefanbeller/git/tree/submodule_i18n_verbose
I think these would be a good foundation for your patch as well, as you can use the
output() function for the desired cases.
Feel free to take these patches as part of your series or adapt
(or be inspired by) as needed.
Thanks,
Stefan
Stefan Beller (2):
submodule.c: move submodule merging to merge-recursive.c
merge-recursive: i18n submodule merge output and respect verbosity
merge-recursive.c | 169 +++++++++++++++++++++++++++++++++++++++++++++-
submodule.c | 168 +--------------------------------------------
submodule.h | 6 +-
3 files changed, 170 insertions(+), 173 deletions(-)
--
2.17.0.255.g8bfb7c0704
next prev parent reply other threads:[~2018-05-10 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 18:26 [PATCH 0/1] warn about auto fast-forwarded submodules during merges Leif Middelschulte
2018-05-10 18:26 ` [PATCH 1/1] Warn about fast-forwarding of submodules during merge Leif Middelschulte
2018-05-10 18:49 ` Stefan Beller
2018-05-10 20:30 ` Leif Middelschulte
2018-05-10 21:19 ` Stefan Beller [this message]
2018-05-10 21:19 ` [PATCH 1/2] submodule.c: move submodule merging to merge-recursive.c Stefan Beller
2018-05-10 21:19 ` [PATCH 2/2] merge-recursive: i18n submodule merge output and respect verbosity Stefan Beller
2018-05-15 1:25 ` Elijah Newren
2018-05-11 0:04 ` [PATCH 0/2] Submodule merging: i18n, verbosity Elijah Newren
2018-05-11 1:00 ` Stefan Beller
2018-05-14 20:57 ` [PATCH 0/1] rebased: inform about auto submodule ff during merge Leif Middelschulte
2018-05-14 20:57 ` [PATCH 1/1] Inform about fast-forwarding of submodules " Leif Middelschulte
2018-05-15 0:41 ` Stefan Beller
2018-05-15 1:17 ` Elijah Newren
2018-05-15 7:34 ` 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=20180510211917.138518-1-sbeller@google.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=leif.middelschulte@gmail.com \
--cc=sandals@crustytoothpaste.ath.cx \
/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).