[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2101957.c21FspBRQs@sven-laptop.home.narfation.org>
Date: Mon, 19 Nov 2012 21:25:23 +0100
From: Sven Eckelmann <sven@...fation.org>
To: Ben Hutchings <bhutchings@...arflare.com>
Cc: b.a.t.m.a.n@...ts.open-mesh.org,
Antonio Quartulli <ordex@...istici.org>,
netdev@...r.kernel.org, Marek Lindner <lindner_marek@...oo.de>,
davem@...emloft.net
Subject: Re: Re: [B.A.T.M.A.N.] [PATCH 04/10] batman-adv: export compatibility version via debugfs
On Monday 19 November 2012 19:40:18 Ben Hutchings wrote:
[...]
> > > I do hope that you're not planning to use unstable debugfs interfaces
> > > indefinitely.
> >
> > Why are you refering to the adding of an file as "incompatible" debugfs
> > interface? I would call it additional information. And the rest of the
> > commit message is talking about *possible* protocol incompatibilies of
> > the network protocol (which caused this uncontrolled erruption of anger
> > in a network maintainer).
>
> I didn't say that. But debugfs tends to be exempted from expectations
> of interface stability or cleanliness (as it's for development, not
> production... right?). It's also an optional feature that might not be
> enabled at compile time or run-time. If BATMAN is ever going to be
> ready for general use it will need stable interfaces that are updated in
> a backward-compatible way and don't depend on debugfs.
Ok, I thought this file was meant for an optional developer information (the
interface to work with batman-adv is in /sys) and concluded too fast that you
are questioning this change because it makes something "unstable" (sry, for
using the wrong term before).
Thanks,
Sven
Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)
Powered by blists - more mailing lists