From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linus <torvalds@linux-foundation.org>
Subject: Re: linux-next: Requirements and process
Date: Wed, 23 Jul 2008 14:28:59 +1000 [thread overview]
Message-ID: <20080723142859.ab9f909d.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20080722153114.e9d44210.randy.dunlap@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 926 bytes --]
Hi Randy,
On Tue, 22 Jul 2008 15:31:14 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
>
> > output from "git describe". Alternatively, you can be based on another
> > tree in linux-next by using:
> >
> > # NEXT_BASE <name of a tree in linux-next>
>
> What do we use for BASE or NEXT_BASE if the base tree is linux-next?
> Just don't use these annotations?
The name from the Next/Trees file in any linux-next release. You should
be very careful doing this if you don't control the other tree, though.
And you should let me know so that I can order the trees appropriately.
This was mainly added for Greg who has 4 quilt series in linux-next that
depend on each other. If you depend on some random tree that changes day
to day your quilt series may no longer apply cleanly on top of it.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-07-23 4:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 5:45 Stephen Rothwell
2008-05-03 6:07 ` Stephen Rothwell
2008-07-22 22:31 ` Randy Dunlap
2008-07-23 4:28 ` Stephen Rothwell [this message]
2008-05-03 6:35 ` Andrew Morton
2008-05-03 7:45 ` Stephen Rothwell
2008-05-03 14:27 ` Andrew Morton
2008-07-23 4:41 ` Stephen Rothwell
2008-05-06 4:48 ` Greg KH
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=20080723142859.ab9f909d.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®