From: Wolfram Sang <wsa@kernel.org>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: Jean Delvare <jdelvare@suse.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for v5.9] i2c: Replace HTTP links with HTTPS ones
Date: Wed, 5 Aug 2020 11:22:23 +0200 [thread overview]
Message-ID: <20200805092223.GJ1229@kunai> (raw)
In-Reply-To: <b7cfd6e3-ee79-b7e2-c7f9-a58e960c3a88@al2klimov.de>
[-- Attachment #1: Type: text/plain, Size: 198 bytes --]
> Yes, I've chosen "the easy way" of git commit --amend:
> Editing the patch file.
> I this a problem?
Usually, yes. It can easily create inconsitencies which make me as a
maintainer suspicious.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-08-05 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-19 19:35 [PATCH for v5.9] i2c: Replace HTTP links with HTTPS ones Alexander A. Klimov
2020-07-21 9:50 ` Jean Delvare
2020-07-21 17:56 ` Alexander A. Klimov
2020-08-05 9:22 ` Wolfram Sang [this message]
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=20200805092223.GJ1229@kunai \
--to=wsa@kernel.org \
--cc=grandmaster@al2klimov.de \
--cc=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 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 NNTP newsgroup(s).