All of 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>
Subject: Re: tty tree change for linux-next
Date: Sat, 1 Aug 2009 10:18:15 -0700	[thread overview]
Message-ID: <20090801171815.GA15259@kroah.com> (raw)
In-Reply-To: <20090801172245.1d3e8b31.sfr@canb.auug.org.au>

On Sat, Aug 01, 2009 at 05:22:45PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Sat, 1 Aug 2009 16:41:04 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > On Fri, 31 Jul 2009 21:39:05 -0700 Greg KH <greg@kroah.com> wrote:
> > >
> > > If there are any problems with the trees, please let me know.
> > 
> > Will do.
> 
> Just a small (but important) thing.  All the tty series patches look like this:
> 
> <summary>
> 
> From: <author>
> 
> <message>
> .
> .
> 
> 
> When I import these, they will all look like they are authored by you and
> use the file name as the one line summary :-( .  "Git quilt-import"
> expects more mail-like patches like:
> 
> From: <author>
> Subject: <summary>
> 
> ..
> 
> So if there is some easy transform you could do on these, it would be
> good.  (There is only one patch that has "Subject:" at the start of the
> <summary>.)  (Subject: followed by From: is ok as well, so 'prepend
> "Subject: " to first line and remove following blank line' would probably
> get you very close.)

Ok, that's not good at all, I just took the patches straight from Alan.
I'll edit them up this weekend to work better (i.e. in the format that
all of my other patches are in, pseudo-mbox headers, which both quilt
and git seem to like.)

Thanks for letting me know,

greg k-h

  reply	other threads:[~2009-08-01 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-01  4:39 tty tree change for linux-next Greg KH
2009-08-01  6:41 ` Stephen Rothwell
2009-08-01  7:22   ` Stephen Rothwell
2009-08-01 17:18     ` Greg KH [this message]
2009-08-01 23:16       ` Stephen Rothwell
2009-08-05 17:08         ` 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=20090801171815.GA15259@kroah.com \
    --to=greg@kroah.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 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.