From: Sam Ravnborg <sam@ravnborg.org>
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>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org
Subject: Re: linux-m68k.git
Date: Tue, 18 Nov 2008 21:59:12 +0100 [thread overview]
Message-ID: <20081118205912.GA23894@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0811182136060.27671@anakin>
On Tue, Nov 18, 2008 at 09:49:01PM +0100, Geert Uytterhoeven 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.
>
> As suggested by David Woodhouse, I grouped the commits by topic. But unlike
> David's suggestion, I used topic branches, not topic repositories. Oh well,
> we'll see...
>
> I also created for-next and for-linus branches. Do they look OK?
>
> If I did something wrong, please let me know.
> This is still experimental stuff, which may be rebased if needed.
>
> In addition, one day I may pull from Ralf's repository that reflects the state
> of Linux/m68k CVS a few commits before our server died...
>
> Thanks for all your (past and future) help, suggestions, tips and tricks!
If you plan to keep it then it would be nice if
you could add a T: entry to MAINTAINERS.
This way we can find it again later...
Sam
next prev parent reply other threads:[~2008-11-18 20:57 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 ` Sam Ravnborg [this message]
2008-11-18 21:19 ` linux-m68k.git Stephen Rothwell
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=20081118205912.GA23894@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--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 \
--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).