From: Linus Torvalds <email@example.com> To: Jonathan Corbet <firstname.lastname@example.org> Cc: Linux Kernel Mailing List <email@example.com>, firstname.lastname@example.org Subject: Re: [GIT PULL] Documentation for 4.20 (or whatever it's called) Date: Wed, 24 Oct 2018 18:02:47 +0100 [thread overview] Message-ID: <CAHk-=wiOWBJVC4che1ZN1dyFR7vNiW_C7LrdGe+LjGW+uZs+3A@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Tue, Oct 23, 2018 at 9:11 AM Jonathan Corbet <firstname.lastname@example.org> wrote: > > This is a fairly typical cycle for documentation. There's some welcome > readability improvements for the formatted output, some LICENSES updates > including the addition of the ISC license, the removal of the unloved and > unmaintained 00-INDEX files, the deprecated APIs document from Kees, more > MM docs from Mike Rapoport, and the usual pile of typo fixes and > corrections. Pulled, Linus
prev parent reply other threads:[~2018-10-24 17:03 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-23 8:11 Jonathan Corbet 2018-10-24 17:02 ` Linus Torvalds [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='CAHk-=wiOWBJVC4che1ZN1dyFR7vNiW_C7LrdGe+LjGW+uZs+3A@mail.gmail.com' \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [GIT PULL] Documentation for 4.20 (or whatever it'\''s called)' \ /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
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 NNTP newsgroup(s).