Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754366Ab0DDN4e (ORCPT ); Sun, 4 Apr 2010 09:56:34 -0400 Received: from londo.lunn.ch ([80.238.139.98]:45759 "EHLO londo.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754251Ab0DDN41 (ORCPT ); Sun, 4 Apr 2010 09:56:27 -0400 Date: Sun, 4 Apr 2010 15:56:21 +0200 From: Andrew Lunn To: The list for a Better Approach To Mobile Ad-hoc Networking Cc: Sven Eckelmann , devel@driverdev.osuosl.org, gregkh@suse.de, linux-kernel@vger.kernel.org Subject: Re: [B.A.T.M.A.N.] [PATCH 4/4] Staging: batman-adv: fix whitespace style issues Message-ID: <20100404135621.GA16351@lunn.ch> References: <1270341625-28764-1-git-send-email-luisbg@ubuntu.com> <201004040312.28481.sven.eckelmann@gmx.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1811 Lines: 36 > Sorry about the conflict, thanks for redoing the changes. Where can I > find the current and development branches? I want to avoid doing this > mistake again in the future. Specially since I'm planning on doing > some janitorial work on Staging for a while if it's OK with you guys. > I see it as nice experience and practice while learning and getting > ready for more valuable contributions :) Sven has told you about how batman uses different repositories. You can find some more information at: http://www.open-mesh.org/wiki/UsingBatmanGit When working on other staging drivers i suggest you work on either the linux-next tree, or contact the driver maintainers and ask if they have there own development tree. Staging drivers tend to be fast moving. They change a lot. What is in the current release kernel, which is effectively 3 months old, can be very different to the latest development version. I've received many patches to things we have fixed months ago and are either waiting in linux-next for the next kernel release, or our in or development tree. I'm sure the same applies to other drivers in staging. Another option for interesting work to get involved in the kernel is to ask GregKH if there is a staging driver which is not being actively worked on. Some drivers just get dumped there and nobody spends the time and effort needed to get them merged. After a while they get thrown out of the staging. You could adopt such a driver, get hold of the hardware and do the work needed to get it out of staging and into the main tree. Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/