From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: mtk.manpages@gmail.com, linux-next@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 21
Date: Fri, 23 May 2014 06:22:22 +0200 [thread overview]
Message-ID: <537ECCFE.5010201@gmail.com> (raw)
In-Reply-To: <20140523080618.618a7eb7@canb.auug.org.au>
Hi Stephen.
On 05/23/2014 12:06 AM, Stephen Rothwell wrote:
> Hi Michael,
>
> On Thu, 22 May 2014 12:45:05 +0200 Michael Kerrisk <mtk.manpages@gmail.com> wrote:
>>
>> On Wed, May 21, 2014 at 9:50 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>> You should use "git fetch" as mentioned in the FAQ on the wiki
>>> (see below).
>>
>> There does not seem to be anything in the rest of your message about
>> this. Did I miss something?
>
> The wiki went away some time ago and so I removed the other reference
> to it, but missed this one. I will try to revise this message today.
> Thanks for noticing - I sometimes wonder if anyone reads my release
> notes :-)
So, where does one find instructions on working with linux-next now?
It would be good to have the basics as part of that mail, or a
pointer to some location where the basics are described.
Currently, one has to hunt a little bit to find something like
http://lists.kernelnewbies.org/pipermail/kernelnewbies/2012-April/005178.html
It would be good if that info was either part of the template mail
or at a stable URL whose content is kept up to date. (I'm willing to
write and host such a page, if for some reason you don't want to,
but I'd like someone to confirm it's accurate.)
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2014-05-24 12:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 7:50 linux-next: Tree for May 21 Stephen Rothwell
2014-05-22 10:45 ` Michael Kerrisk
2014-05-22 22:06 ` Stephen Rothwell
2014-05-23 4:22 ` Michael Kerrisk (man-pages) [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-21 6:44 Stephen Rothwell
2020-05-21 14:12 Stephen Rothwell
2020-05-21 15:09 ` Daniel Thompson
2019-05-21 5:14 Stephen Rothwell
2019-05-21 5:48 ` Masahiro Yamada
2019-05-21 6:18 ` Stephen Rothwell
2015-05-21 8:57 Stephen Rothwell
2013-05-21 5:03 Stephen Rothwell
2012-05-21 9:05 Stephen Rothwell
2012-05-21 15:09 ` Randy Dunlap
2012-05-21 15:41 ` Stephen Rothwell
2012-05-21 15:44 ` Stephen Rothwell
2010-05-21 6:51 Stephen Rothwell
2009-05-21 8:14 Stephen Rothwell
2008-05-21 5:59 Stephen Rothwell
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=537ECCFE.5010201@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 NNTP newsgroup(s).