From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg KH <gregkh@linuxfoundation.org>,
dalias@libc.org, linux-sh@vger.kernel.org,
ysato@users.sourceforge.jp
Subject: Re: patch "maple: make maple_bus_type static and const" added to char-misc-testing
Date: Sun, 07 Jan 2024 22:46:51 +0100 [thread overview]
Message-ID: <bde9cdb0b4e2cee74dd74aa7496a1d87f90f136e.camel@physik.fu-berlin.de> (raw)
In-Reply-To: <CAMuHMdV=sCNZ2KdSb8B66wYYbNMjNEm6quRRbVMZVRVJ3npJ9A@mail.gmail.com>
On Fri, 2024-01-05 at 10:13 +0100, Geert Uytterhoeven wrote:
> Everybody goes on holidays, once in a while.
>
> But, you are unhappy about Linus Torvalds announcing during your
> holidays that there would be an extra rc, postponing the merge window
> by one week? And without this postponing you would have missed the
> merge window for sure, so this delay is actually beneficial to you?
No, I'm unhappy about the work being taken away from me just because I
went on vacation. I'm still practicing all this being relatively new
to the kernel work, after all.
> The merge window is the period when Linus Torvalds merges new
> developments for the next kernel release.
> The merge window is not the period when maintainers review and collect
> new developments for the next kernel release.
I have done some reviews during the merge window before. It's not like the
merge window is just open for one day. I know it's not how it's supposed
to be, but I am also not sending huge pull requests, so it isn't really
an issue at the moment.
> If you are on holidays just before or during the merge window, you
> should prepare your branches, and send pull requests, before the merge
> window opens. Several maintainers have already sent pull requests
> (the first arrived almost 2 weeks ago).
I am not getting paid for doing kernel stuff. I am doing this completely in
my free time, on top of all the time and effort I am investing in Debian to
still provide a distribution for older architectures. And, naturally, my
primary job has priority over what I do for the kernel.
Thus, I cannot always plan my kernel work with the upstream schedule.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2024-01-07 21:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 13:37 patch "maple: make maple_bus_type static and const" added to char-misc-testing gregkh
2024-01-04 13:48 ` John Paul Adrian Glaubitz
2024-01-04 13:57 ` Greg KH
2024-01-04 14:02 ` John Paul Adrian Glaubitz
2024-01-04 14:16 ` Geert Uytterhoeven
2024-01-04 14:20 ` Greg KH
2024-01-04 14:41 ` John Paul Adrian Glaubitz
2024-01-04 16:01 ` Geert Uytterhoeven
2024-01-04 18:44 ` John Paul Adrian Glaubitz
2024-01-05 7:34 ` Greg KH
2024-01-05 9:38 ` John Paul Adrian Glaubitz
2024-01-05 9:45 ` Greg KH
2024-01-07 21:39 ` John Paul Adrian Glaubitz
2024-01-05 9:13 ` Geert Uytterhoeven
2024-01-07 21:46 ` John Paul Adrian Glaubitz [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=bde9cdb0b4e2cee74dd74aa7496a1d87f90f136e.camel@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-sh@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).