From: Gabriele Mazzotta <gabriele.mzt@gmail.com>
To: git@vger.kernel.org
Cc: paulus@ozlabs.org
Subject: Re: [PATCH] gitk: Do not mistake unchanged lines with submodule changes
Date: Sun, 21 Oct 2018 18:39:39 +0200 [thread overview]
Message-ID: <fcef23d5-e2b3-cb3a-9ccf-75a0cc126d0b@gmail.com> (raw)
In-Reply-To: <20181021163401.4458-1-dummy@example.com>
On 21/10/18 18:34, Dummy Name wrote:
> From: Gabriele Mazzotta <gabriele.mzt@gmail.com>
>
> Unchanged lines are prefixed with a white-space, thus unchanged lines
> starting with either " <" or " >" are mistaken for submodule changes.
> Check if a line starts with either " <" or " >" only if we listing
> the changes of a submodule.
>
> Signed-off-by: Gabriele Mazzotta <gabriele.mzt@gmail.com>
Hi,
I accidentally pressed Enter before I could set the committer
to the correct value. I can resend the patch if necessary.
Regards,
Gabriele
next prev parent reply other threads:[~2018-10-21 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-21 16:34 [PATCH] gitk: Do not mistake unchanged lines with submodule changes Dummy Name
2018-10-21 16:39 ` Gabriele Mazzotta [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-23 17:00 Gabriele Mazzotta
2019-09-15 23:08 ` Paul Mackerras
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fcef23d5-e2b3-cb3a-9ccf-75a0cc126d0b@gmail.com \
--to=gabriele.mzt@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@ozlabs.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.