From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for May 12
Date: Mon, 12 May 2008 08:22:05 -0700 [thread overview]
Message-ID: <20080512082205.8678bbaf.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080512150418.603e29cf.sfr@canb.auug.org.au>
On Mon, 12 May 2008 15:04:18 +1000 Stephen Rothwell wrote:
> Hi all,
>
> News: I am now providing patches relative to the latest tag in Linus'
> tree. I propose to stop providing complete tar balls as they are so
> large and people will have recent versions of Linus's tree anyway (I
> assume). The patches will be named "patch-<upstream tag>-<next tag>".
Oh well. For the record, I don't mind using patches instead of
complete tarballs, but I would prefer that the patches be relative
to something like a daily -git snapshot so that using git is not
required at all.
---
~Randy
next prev parent reply other threads:[~2008-05-12 15:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 5:04 linux-next: Tree for May 12 Stephen Rothwell
2008-05-12 15:22 ` Randy Dunlap [this message]
2008-05-13 0:30 ` Stephen Rothwell
2008-05-13 1:30 ` Randy Dunlap
-- strict thread matches above, loose matches on Subject: below --
2009-05-12 5:46 Stephen Rothwell
2010-05-12 6:46 Stephen Rothwell
2011-05-12 4:23 Stephen Rothwell
2014-05-12 6:59 Stephen Rothwell
2015-05-12 6:20 Stephen Rothwell
2016-05-12 5:49 Stephen Rothwell
2017-05-12 3:12 Stephen Rothwell
2017-05-12 3:13 ` Stephen Rothwell
2020-05-12 12:54 Stephen Rothwell
2021-05-12 7:56 Stephen Rothwell
2022-05-12 10:13 Stephen Rothwell
2023-05-12 2:51 Stephen Rothwell
2025-05-12 10:21 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=20080512082205.8678bbaf.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.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).