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: Arnd Bergmann <arnd@arndb.de>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: New Char/Misc tree to be added to linux-next
Date: Mon, 14 Nov 2011 22:01:02 -0800	[thread overview]
Message-ID: <20111115060102.GA29942@kroah.com> (raw)
In-Reply-To: <20111115125939.dd90968640fc7c50bd9a4c77@canb.auug.org.au>

On Tue, Nov 15, 2011 at 12:59:39PM +1100, Stephen Rothwell wrote:
> Hi Greg,
> 
> On Mon, 14 Nov 2011 16:14:19 -0800 Greg KH <greg@kroah.com> wrote:
> >
> > Arnd and I are going to maintain the drivers/char/* and drivers/misc/*
> > directories with the goal of getting them under control, or at least a
> > false-sense of control :)
> > 
> > So could you please add my new git tree:
> > 	git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git
> > 
> > which contains the two branches, "char-misc-linus" to hold patches to
> > send to Linus for this merge window, and "char-misc-next" to hold
> > patches for the next merge window.
> 
> OK, I will add this tree tomorrow with you and Arnd as contacts.  [Aside:
> did you consider naming the branches merely "fixes" (or something) and
> "next"?]

I was using the same branch naming that I used for my other trees.  If
that's unwieldy, I can easily change them, just let me know, but I would
like to be consistant across all of my trees for the sake of my muscle
memory, and my helper-scripts.

thanks,

greg k-h

  reply	other threads:[~2011-11-15  6:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-15  0:14 New Char/Misc tree to be added to linux-next Greg KH
2011-11-15  1:59 ` Stephen Rothwell
2011-11-15  6:01   ` Greg KH [this message]
2011-11-15  6:05     ` 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=20111115060102.GA29942@kroah.com \
    --to=greg@kroah.com \
    --cc=arnd@arndb.de \
    --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.