From: Marek Lindner <lindner_marek@yahoo.de>
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.] batmand in debian
Date: Sun, 2 Dec 2007 15:59:30 +0100 [thread overview]
Message-ID: <200712021559.30672.lindner_marek@yahoo.de> (raw)
In-Reply-To: <200712012012.01657.holger@layer-acht.org>
Hi,
> > > Which means, we can now prepare 0.3 for Debian/experimental, or to
> > > unstable if you you think that's better.
> >
> > I think unstable would be fine for the moment or any objections ?
>
> Then 0.2 would be "gone".. as I understood you, you have these two branches
> for a reason... if not, let's go for 0.3~svn_revision in unstable.
yes - 0.3 is not stable yet. I'm not in a hurry. If you think it is better to
go with experimental first I wont object to that.
Another option would be to delay this question for a month or so. I know that
during the CCC event (at the end of the yea)r a lot of testing and hacking is
planned. Lets see where we are after that.
Greetings,
Marek
next prev parent reply other threads:[~2007-12-02 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-01 11:34 [B.A.T.M.A.N.] batmand in debian Holger Levsen
2007-12-01 17:39 ` Marek Lindner
2007-12-01 19:12 ` Holger Levsen
2007-12-02 14:59 ` Marek Lindner [this message]
2007-12-03 15:23 ` 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=200712021559.30672.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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