public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven.eckelmann@gmx.de>
To: Luis de Bethencourt <luisbg@ubuntu.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 4/4] Staging: batman-adv: fix whitespace style issues
Date: Sun, 4 Apr 2010 12:46:33 +0200	[thread overview]
Message-ID: <201004041246.38682.sven.eckelmann@gmx.de> (raw)
In-Reply-To: <p2x506b70dc1004031845p81705070o325d93f839c80e9a@mail.gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 1934 bytes --]

On Sunday 04 April 2010 03:45:52 Luis de Bethencourt wrote:
> Sorry about the conflict, thanks for redoing the changes. Where can I
> find the current and development branches?

The development is currently done in different branches and SCMs outside the 
kernel. Andrew Lunn prepares a maint branch for submission to GregKH and sends 
it to him for staging.

Most of the development of future features are done in
 http://downloads.open-mesh.org/svn/batman/ under trunk/batman-adv-kernelland/
This is usually not what you deal with as only the maint branch is submitted 
for inclusion into linux staging. Nevertheless all changes in svn for batman-
adv-kernelland are automatically imported into
http://git.open-mesh.net/?p=batman-adv (branch master).

The maint work is now done inside the maint branch of that git repository. It 
doesn't contain the whole linux tree and holds all files to build an external 
module (used for example in OpenWRT and Debian). When Andrew thinks that it is 
ready to be send to GregKH, he will do a subtree merge into linus (holds the 
linux tree) and then rebase the changes in a private branch. This is needed to 
have the correct directories inside the patches and that files removed/added 
for the kernel are still being deleted/available.

So doing your changes against the git maint branch is the correct way in most 
situations.

> 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 :)

Yes, contributors are welcome.

There is also a userspace part which must also work with your changes. One 
problem was spotted by Marek. So it is maybe a good idea to send changes over 
the b.a.t.m.a.n. mailing list.

Best regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-04-04 10:46 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <batman-adv>
     [not found] ` <1270341625-28764-1-git-send-email-luisbg@ubuntu.com>
2010-04-04  1:12   ` [B.A.T.M.A.N.] [PATCH 4/4] Staging: batman-adv: fix whitespace style issues Sven Eckelmann
2010-04-04  1:24     ` [B.A.T.M.A.N.] [PATCHv2-maint] " Sven Eckelmann
2010-04-04 17:09       ` Marek Lindner
2010-04-04 17:51         ` Luis de Bethencourt
2010-04-04  1:44     ` [B.A.T.M.A.N.] [PATCHv2-trunk] " Sven Eckelmann
2010-04-04  2:48       ` Marek Lindner
2010-04-04 16:33       ` [B.A.T.M.A.N.] [PATCH] batctl: Parse allowed settings for sysfs without whitespace before newline Sven Eckelmann
2010-04-06  5:33         ` Marek Lindner
2010-04-04  1:45     ` [B.A.T.M.A.N.] [PATCH 4/4] Staging: batman-adv: fix whitespace style issues Luis de Bethencourt
2010-04-04 10:46       ` Sven Eckelmann [this message]
2010-04-04 11:10         ` Luis de Bethencourt
2010-04-04 11:30           ` Sven Eckelmann
2010-04-04 12:39             ` Luis de Bethencourt
2010-04-04 14:42               ` Marek Lindner
2010-04-04 15:02                 ` Luis de Bethencourt
2010-04-04 15:14                   ` Sven Eckelmann
2010-04-04 15:19                     ` Luis de Bethencourt
2010-04-04 13:56       ` Andrew Lunn
2010-04-04 14:56         ` Luis de Bethencourt

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=201004041246.38682.sven.eckelmann@gmx.de \
    --to=sven.eckelmann@gmx.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.org \
    --cc=luisbg@ubuntu.com \
    /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