From: Holger Levsen <holger@layer-acht.org>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] get the branches explained
Date: Tue, 5 Feb 2008 11:34:51 +0100 [thread overview]
Message-ID: <200802051134.52933.holger@layer-acht.org> (raw)
In-Reply-To: <200802042325.02853.lindner_marek@yahoo.de>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
Hi Marek,
On Monday 04 February 2008 16:25, Marek Lindner wrote:
> in the last months many new branches were created and many numbers are
> floating around which caused much confusion. Here comes a brief summary why
> these branches and numbers were created, what they are good for and who is
> behind it:
Cool, thanks. Please put this summary also either on the website or somewhere
in svn or both :-)
regards,
Holger
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-02-05 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 15:25 [B.A.T.M.A.N.] get the branches explained Marek Lindner
2008-02-05 10:34 ` Holger Levsen [this message]
2008-02-05 22:51 ` Marek Lindner
2008-02-06 9:17 ` Holger Levsen
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=200802051134.52933.holger@layer-acht.org \
--to=holger@layer-acht.org \
--cc=b.a.t.m.a.n@open-mesh.net \
/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