From mboxrd@z Thu Jan 1 00:00:00 1970 From: Geert Uytterhoeven Subject: linux-m68k.git Date: Tue, 18 Nov 2008 21:49:01 +0100 (CET) Message-ID: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: Received: from edna.telenet-ops.be ([195.130.132.58]:36795 "EHLO edna.telenet-ops.be" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752200AbYKRUtG (ORCPT ); Tue, 18 Nov 2008 15:49:06 -0500 Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Linux/m68k Cc: Ralf Baechle , David Woodhouse , Stephen Rothwell , Linux Kernel Development , linux-next@vger.kernel.org (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! Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds