From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
David Woodhouse <dwmw2@infradead.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: linux-m68k.git
Date: Wed, 19 Nov 2008 08:19:51 +1100 [thread overview]
Message-ID: <20081119081951.a1a33403.sfr@canb.auug.org.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0811182136060.27671@anakin>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
Hi Geert,
On Tue, 18 Nov 2008 21:49:01 +0100 (CET) Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> (Finally) I created an experimental git tree for Linux/m68k:
> http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git
>
> It contains more or less all patches I had in my quilt series at
> http://www.kernel.org/pub/linux/kernel/people/geert/linux-m68k-patches-2.6/
> A notable exception is m68k-PRIVATE-m68k-changes.diff, which hardcoded ARCH to
> m68k.
>
> I also created for-next and for-linus branches. Do they look OK?
They look good. I have added the for-linus branch as my m68k-current
tree and changed my m68k tree over to the for-next branch.
> If I did something wrong, please let me know.
> This is still experimental stuff, which may be rebased if needed.
That's fine as long as the commits in the for-next branch are: posted
somewhere relevant, reviewed, tested and destined for the next merge
window. (None of these requirements have changed from what should have
been in your quilt tree.)
I expect the for-linus branch to be fixes and stuff for the current
release.
--
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-11-18 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 20:49 linux-m68k.git Geert Uytterhoeven
2008-11-18 20:59 ` linux-m68k.git Sam Ravnborg
2008-11-18 21:19 ` Stephen Rothwell [this message]
2008-11-19 8:44 ` linux-m68k.git Geert Uytterhoeven
2008-11-19 9:28 ` linux-m68k.git Stephen Rothwell
2008-11-19 6:45 ` linux-m68k.git Michael Schmitz
2008-11-19 8:13 ` linux-m68k.git Ralf Baechle
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=20081119081951.a1a33403.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=ralf@linux-mips.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