All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Please add the tiny tree to linux-next
Date: Mon, 22 Sep 2014 10:53:04 -0700	[thread overview]
Message-ID: <20140922175301.GA27348@thin> (raw)

Hi Stephen,

Can you please add the tiny tree, branch tiny/next of
https://git.kernel.org/pub/scm/linux/kernel/git/josh/linux.git , to
linux-next?

I'll be using this tree to upstream various patches for Linux kernel
tinification.  I plan to use topic branches under tiny/* for separate
topics, typically based on the previous -rc1, merging them into
tiny/next; when the merge window opens, I'll submit a pull request for
tiny/next and start merging new tiny/* topic branches into a
tiny/next-next branch or similar that will become the new tiny/next
after tiny/next gets merged.

- Josh Triplett

             reply	other threads:[~2014-09-22 17:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 17:53 Josh Triplett [this message]
2014-09-22 22:34 ` Please add the tiny tree to linux-next Stephen Rothwell
2014-09-22 22:51   ` josh
2014-09-22 23:44     ` 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=20140922175301.GA27348@thin \
    --to=josh@joshtriplett.org \
    --cc=linux-kernel@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.