[Olsr-dev] NL80211 link quality patch and GIT repository

[Kees-Jan Hermans]

Ok, thanks. Turns out that what I thought was new, was old, and vice
versa. Spent some of the weekend adapting a patch against the old code.
My mistake I suppose - teach me the basics of this here project ;-)

Anyway, some patching up was necessary anyhow (mostly, unfortunately,
due to the fact that there is no stable nl80211 userland API on Linux,
differing wildly among distributions and no real sure way to know what
version you're dealing with on the basis of #defines and whatnot)

Which leads me to another question: is there something in the course of
'make' that I could use to create a 'configure' like situation
(discovery of certain uses of header files, function prototypes and
defines) ?

Sincerely,

KJ

On Mon, 2012-07-09 at 16:49 +0200, Henning Rogge wrote:
> On 07/09/2012 04:45 PM, Kees-Jan Hermans wrote:
> > Dear all,
> >
> > I've been working on renewing the patch for using wireless lan metrics
> > as part of the link quality cost calculation, but I've been a bit
> > confused as to how the repository works; it seems that the default
> > 'master' branch is old, and the 'stable' branch is where everyone is
> > committing their new code against. Is that correct? I'm just asking,
> > because in other places, such nomenclature would suggest a different,
> > and opposite, function.
> 
> Yes, thats right.
> 
> We were also in the process of discussing a change in the "where to 
> commit and how to do it" policy here when I got hit by an "eat up a 
> whole week of time" thing...
> 
> Hope we will restart the discussion soon and sort it out.
> 
> Henning
> 
>