From: Diego Viola <diego.viola@gmail.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] README: cosmetic fixes
Date: Mon, 18 Jan 2016 17:53:02 -0200 [thread overview]
Message-ID: <CA+ToGPFL5bC2GSir9O2A+bF51wfDJoAh4NCex=OGH2cmxwEm5g@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1601181042170.21446@cbobk.fhfr.pm>
On Mon, Jan 18, 2016 at 7:44 AM, Jiri Kosina <jikos@kernel.org> wrote:
> On Sun, 17 Jan 2016, Diego Viola wrote:
>
>> Is there a reason this patch didn't make it for 4.5?
>
> Diego, this is a second time I am CCed on some super-super-trivial patch
> from you, and you keep to be very persistent regarding the urge of pushing
> everything upstream ASAP.
>
> Please understand that there are much more important things that need to
> end up in a particular kernel release, and purely cosmetic fixes (such as
> this one) simply have to wait for the particular maintainer to clean up
> low priority items (such as this one) from his queue.
>
> Thanks,
>
> --
> Jiri Kosina
> SUSE Labs
>
The thing I'm unsure about is that the pull request contained trivial
changes from others as well, and my patch was trivial, yes.
So why not include my changes with the other trivial changes as well?
Diego
next prev parent reply other threads:[~2016-01-18 19:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-05 19:50 Diego Viola
2015-12-10 18:34 ` Jonathan Corbet
2015-12-11 3:06 ` Diego Viola
2016-01-17 22:54 ` Diego Viola
2016-01-18 9:44 ` Jiri Kosina
2016-01-18 13:41 ` Diego Viola
2016-01-18 19:53 ` Diego Viola [this message]
2016-01-18 22:40 ` Jonathan Corbet
2016-01-19 1:32 ` Diego Viola
2016-01-19 2:40 ` Diego Viola
2016-01-19 6:24 ` Diego Viola
2016-01-25 19:40 ` Jonathan Corbet
2016-01-28 18:23 ` Diego Viola
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='CA+ToGPFL5bC2GSir9O2A+bF51wfDJoAh4NCex=OGH2cmxwEm5g@mail.gmail.com' \
--to=diego.viola@gmail.com \
--cc=corbet@lwn.net \
--cc=jikos@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
all inboxes | Powered by JetHome®