LKML Archive on
 help / color / Atom feed
From: Linus Torvalds <>
To: Sedat Dilek <>
Cc: Linux Kernel Mailing List <>
Subject: Re: Linux 5.12-rc1
Date: Mon, 1 Mar 2021 13:34:40 -0800
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Mar 1, 2021 at 12:35 AM Sedat Dilek <> wrote:
> I wondered why there was approx. for 6 days no commits and got an
> answer from an LWN posting "5.12 Merge window delayed".
> Unsure, if there was a posting to LKML?

There was no posting to lkml because lkml doesn't take html emails,
and I only had mobile data (and not even that for the first 24 hours
or so - even cell towers were down).

I did send updates to several top-level maintainers and to the mailing list, so a lot of people knew about it, but
they in turn probably only ended up mentioning it on a need-to-know
basis. As you mention, LWN did have a mention of it, but you'd have to
find it.

In normal times I would have just taken a laptop to the nearest
Starbucks and worked that way, but not in the pandemic. Plus the local
highway was actually shut down for three days because of downed trees
on the road (this was not a Texas-style electricity generation problem
- it was literally thousands of trees falling all over. We had one
miss our house by a couple of meters).

Two weeks later, and the roadways are still littered with trees and
tons of branches everywhere you drive.

And I didn't have a generator because our local power lines are
actually buried, and we very seldom lose electricity. But when all the
feeder lines are down because trees fell over, and it takes a week
first for the tree crews to clear the roads and then the electric
crews to replace literally miles of electric cable, it doesn't really
help all that much that the local lines are buried and all in good
working order ;)

> Anyway, if you are not able to make your work someone else should jump
> in like Greg did once.

It was an option, it didn't seem worth it.

And part of _that_ was that it looked like "ok, a couple of days", and
then it just kept being "one more day" for several days.

A lot of people lost power for just a day or two.

The area I live in probably wasn't a huge priority, because it's
somewhat sparsely populated, and nice and wooded.

Which is really nice most of the time. It's not quite so nice when you
can hear the trees keep falling around you, and you know you have a
few really big ones right next to the house.. ;^p


  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01  8:35 Sedat Dilek
2021-03-01 21:34 ` Linus Torvalds [this message]
2021-03-06  7:01   ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2021-03-01  0:29 Linus Torvalds
2021-03-01 20:53 ` Guenter Roeck

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

LKML Archive on

Archives are clonable:
	git clone --mirror lkml/git/0.git
	git clone --mirror lkml/git/1.git
	git clone --mirror lkml/git/2.git
	git clone --mirror lkml/git/3.git
	git clone --mirror lkml/git/4.git
	git clone --mirror lkml/git/5.git
	git clone --mirror lkml/git/6.git
	git clone --mirror lkml/git/7.git
	git clone --mirror lkml/git/8.git
	git clone --mirror lkml/git/9.git
	git clone --mirror lkml/git/10.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ \
	public-inbox-index lkml

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone