Thinking about that some further -- I'd like to hear more about what
you're trying to do, since I'm not absolutely convinced that
network-layer multicast is what you want to be using. (An
application-layer protocol might be more suitable, such as the flooding
algorithm used by AHCP, or even
Hi!
On Tue, Mar 1, 2011 at 8:52 AM, Juliusz Chroboczek j...@pps.jussieu.fr wrote:
Independently of the OpenWRT issues (which I'm confident Gabriel will
solve), do people want the babeld, babelz and ahcpd repositories to move
to Git? Git sucks, but it sucks less than it used to, and I'm okay
To stir things even more: why not Mercurial? ;-)
olsr moved from mercurial to git :)
Saverio
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/babel-users
To stir things even more: why not Mercurial? ;-)
Git is an infuriating piece of software, but with a great ecosystem.
Darcs is a great piece of software, but with no ecosystem to speak about.
Mercurial has the user-friendliness of Git with an ecosystem akin to Darcs'.
Sorry, but you started ;-)
Same goes for multicast -- I see no reason why multicast routing should
be linked to a particular unicast routing protocol, and intend to work
on a more general solution.
Yes this seems the good approach
Don't hold your breath, though, my main
priority right now is to finish publishing the Babel
Git! Git! Git! Git! Git!
2011/3/1 Juliusz Chroboczek j...@pps.jussieu.fr:
To stir things even more: why not Mercurial? ;-)
Git is an infuriating piece of software, but with a great ecosystem.
Darcs is a great piece of software, but with no ecosystem to speak about.
Mercurial has the
Git! Git! Git! Git! Git!
you are so young :)
Saverio
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/babel-users
7 matches
Mail list logo
