All of lore.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: Tree for Aug 9
Date: Fri, 09 Aug 2013 09:53:36 -0700	[thread overview]
Message-ID: <52051E90.3090507@infradead.org> (raw)
In-Reply-To: <20130809161540.f65dd6412ac59d49a32881c8@canb.auug.org.au>

On 08/08/13 23:15, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20130808:
> 
> *crickets*
> 
> ----------------------------------------------------------------------------
> 
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one.  You should use "git fetch" as mentioned in the FAQ on the wiki
> (see below).


and if you are not using git but are using tarballs instead,
where is the patch file?

thanks,
-- 
~Randy

  reply	other threads:[~2013-08-09 16:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09  6:15 linux-next: Tree for Aug 9 Stephen Rothwell
2013-08-09  6:15 ` Stephen Rothwell
2013-08-09 16:53 ` Randy Dunlap [this message]
2013-08-09 23:46   ` Stephen Rothwell
2013-08-10 22:15 ` linux-next: Tree for Aug 9 (staging/ozwpan) Randy Dunlap
2013-08-10 22:15   ` Randy Dunlap
2013-08-10 23:15   ` Randy Dunlap
2013-08-10 23:15     ` Randy Dunlap
2013-08-11  9:04     ` Gujare, Rupesh
2013-08-11  9:04       ` Gujare, Rupesh
2013-08-12  6:22       ` Greg Kroah-Hartman
  -- strict thread matches above, loose matches on Subject: below --
2024-08-09  4:31 linux-next: Tree for Aug 9 Stephen Rothwell
2023-08-09  6:02 Stephen Rothwell
2022-08-09  2:26 Stephen Rothwell
2021-08-09 11:39 Stephen Rothwell
2019-08-09  8:03 Stephen Rothwell
2019-08-10 16:23 ` Anders Roxell
2019-08-10 17:42   ` Christoph Hellwig
2018-08-09  8:06 Stephen Rothwell
2017-08-09  7:05 Stephen Rothwell
2016-08-09  3:52 Stephen Rothwell
2012-08-09  3:13 Stephen Rothwell
2011-08-09  3:57 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=52051E90.3090507@infradead.org \
    --to=rdunlap@infradead.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.