LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Alasdair G Kergon <agk@redhat.com>,
	Jean Delvare <khali@linux-fr.org>,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: Re: linux-next: quilt series
Date: Thu, 14 Feb 2008 12:42:09 -0800	[thread overview]
Message-ID: <20080214204209.GA17277@kroah.com> (raw)
In-Reply-To: <20080215014210.73c71078.sfr@canb.auug.org.au>

On Fri, Feb 15, 2008 at 01:42:10AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> To make my life easier, can I ask that the series file for any quilt trees in the linux-next tree have a comment at the top to identify their base (either a SHA1 or some other ref in Linus' tree).  Like this:
> 
> # BASE <SHA1 or ref>

My trees are now marked with this.

> Also, if you only want a subset of the series file included, you can mark the patches with
> 
> # NEXT_PATCHES_START
> 	.
> 	.
> # NEXT_PATCHES_END

Oh, that's nice.

Can we write these things down somewhere on the web so that I, and
others, remember them in a few months?  :)

thanks,

greg k-h

  parent reply	other threads:[~2008-02-14 20:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-14 14:42 linux-next: quilt series Stephen Rothwell
2008-02-14 15:04 ` Jean Delvare
2008-02-14 15:08   ` Jiri Kosina
2008-02-14 15:14     ` Stephen Rothwell
2008-02-14 15:08   ` Stephen Rothwell
2008-02-14 16:42 ` Randy Dunlap
2008-02-14 23:43   ` Stephen Rothwell
2008-02-14 19:20 ` Bartlomiej Zolnierkiewicz
2008-02-14 23:47   ` Stephen Rothwell
2008-02-14 20:42 ` Greg KH [this message]
2008-02-14 23:50   ` Stephen Rothwell
2008-02-19  0:40   ` Frank Seidel
2008-02-19 17:56     ` 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=20080214204209.GA17277@kroah.com \
    --to=greg@kroah.com \
    --cc=agk@redhat.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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).