From: "Oscar Megia López" <megia.oscar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: I need help to send v2 patch on linux-ext4 at vger.kernel.org
Date: Thu, 27 Jul 2023 20:06:19 +0200 [thread overview]
Message-ID: <877cqlmdpg.fsf@gmail.com> (raw)
Hi
I have submitted a patch to linux-ext4 at vger.kernel.org mailing list
and they have responded with whatever changes they think are necessary.
Can someone help me by telling me the steps I need to take to send v2?
I don't know where ask it.
Do I have to create a new branch?
Is modifying the source in the same branch enough?
Do I have to do a git pull on the patch branch before the changes?
Do I have to to commit the changes before running
git format-patch --in-reply-to=20230423082349.53474-1-megia.oscar@gmail.com --cover-letter -o outgoing_v2/ master?
--in-reply-to= points to the v1 patch cover-letter or v1 1/1 mail?.
Please, is my first time to send a patch version's v2 and I didn't find
any place where explain step by step how to do it.
I tried several steps, but I get errors or resend v1 patch too.
--
Regards
Oscar Megia López
next reply other threads:[~2023-07-27 18:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 18:06 Oscar Megia López [this message]
[not found] ` <8ef54195-4102-0c6c-e14d-efc9bc45cddc@web.de>
2023-07-28 6:22 ` Contributing subsequent patch versions Oscar Megia López
2023-07-28 18:10 ` Theodore Ts'o
2023-07-30 6:23 ` Oscar Megia López
[not found] ` <85938916-305c-c8b9-89db-45e522616526@web.de>
2023-07-30 10:12 ` Greg KH
[not found] ` <61a79836-3981-b6e0-cbbf-fe03507dbea4@web.de>
2023-07-28 18:36 ` Oscar Megia López
2023-07-28 19:59 ` Theodore Ts'o
2023-07-30 7:10 ` Oscar Megia López
[not found] ` <27a41740-9cdd-2adf-f3cc-1f9a2d9f2ed1@web.de>
2023-07-30 7:56 ` Oscar Megia López
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=877cqlmdpg.fsf@gmail.com \
--to=megia.oscar@gmail.com \
--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