From: "Oscar Megia López" <megia.oscar@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Markus Elfring <Markus.Elfring@web.de>,
kernel-janitors@vger.kernel.org, linux-ext4@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Dan Carpenter <error27@gmail.com>
Subject: Re: Contributing subsequent patch versions
Date: Sun, 30 Jul 2023 09:10:48 +0200 [thread overview]
Message-ID: <87pm49nabr.fsf@gmail.com> (raw)
In-Reply-To: <20230728195959.GB607743@mit.edu> (Theodore Ts'o's message of "Fri, 28 Jul 2023 15:59:59 -0400")
"Theodore Ts'o" <tytso@mit.edu> writes:
> On Fri, Jul 28, 2023 at 08:36:50PM +0200, Oscar Megia López wrote:
>> I don't know correct steps to send patch's v2 as above instance. Sorry,
>> but I need step by step instructions, if not I think that I can make
>> mistakes and I don't want. Sorry, but my experience says that is very
>> easy make mistakes when I am newbie.
>
> We all make mistakes; don't worry about it! This includes myself,
> which is why I often will run:
>
> git format-patch -o /tmp/p -5
>
> <then examine the patches in /tmp/p very carefully to make sure they make sense>
>
> before I run
>
> git send-email /tmp/e --to linux-<subsystem>
>
> where I have a bunch of aliases in ~/.mail_aliases, e.g.:
>
...
Thank you very much Ted for your help and your time. I really appreciate
it.
I apologize for my doubts, but I've always been told that I'm
different because I doubt everything. Sometimes is good and sometimes is
not good.
In my experience, I believe that asking for help from someone who knows
much more is the right way to act when you don't know how solve issue.
--
Regards
Oscar Megia López
next prev parent reply other threads:[~2023-07-30 7:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 18:06 I need help to send v2 patch on linux-ext4 at vger.kernel.org Oscar Megia López
[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
2023-07-30 8:23 ` Markus Elfring
2023-07-30 10:12 ` Greg KH
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 [this message]
[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=87pm49nabr.fsf@gmail.com \
--to=megia.oscar@gmail.com \
--cc=Markus.Elfring@web.de \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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.