linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: dragoran <drago01@gmail.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	jt@hpl.hp.com, linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: iwlist and network-manager bug report
Date: Fri, 14 Sep 2007 22:10:41 +0200	[thread overview]
Message-ID: <46EAEAC1.5020105@gmail.com> (raw)
In-Reply-To: <1189800306.20386.6.camel@xo-3E-67-34.localdomain>

Dan Williams wrote:
> On Fri, 2007-09-14 at 21:12 +0200, dragoran wrote:
>  =20
>> Dan Williams wrote:
>>    =20
>>> On Thu, 2007-09-13 at 20:18 +0200, Johannes Berg wrote:
>>>  =20
>>>      =20
>>>> On Thu, 2007-09-13 at 09:11 +0200, Johannes Berg wrote:
>>>>
>>>>    =20
>>>>        =20
>>>>> Ok. I'll have to do some more extensive tests but in my last test=
 with
>>>>> zd1211 it wouldn't display anything. Might be a different issue, =
but
>>>>> scanning manually showed things.
>>>>>      =20
>>>>>          =20
>>>> Cool, I was totally wrong, seems the fact that it didn't display
>>>> anything was unrelated. I just tried again and NM 0.6.5 as shipped=
 by
>>>> debian/unstable actually manages to display the =C3=BC umlaut that=
 is
>>>> supposed to be the \xfc character.
>>>>
>>>> Btw. Will there ever be a 0.7 release? :)
>>>>    =20
>>>>        =20
>>> I've been burning the midnight oil on it for the past few weeks, ch=
eck
>>> NM and applet changelogs.  Still not quite there yet, there's some =
core
>>> work left to do getting NM to talk to the settings daemons (ie,
>>> nm-client or knetworkmanager) correctly, getting GUI bits for Conne=
ction
>>> editing in the applet, and making sure the relevant settings are
>>> honored.
>>>  =20
>>>      =20
>> might be a bit OT but:
>> are you still planning to include it in F8 ? seems that the snapshot=
=20
>> didn't make it into test2 ..
>>    =20
>
> There was a snapshot queued, but it really sucked, and was thankfully
> dropped.=20
ok I noticed thats broken after getting it from koji ...
>  Look for something in rawhide this week that actually works.
>
>  =20
ok :)


-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2007-09-14 20:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-11 16:07 iwlist and network-manager bug report Johannes Berg
2007-09-12 15:22 ` Dan Williams
2007-09-12 17:01   ` Jean Tourrilhes
2007-09-13  7:11     ` Johannes Berg
2007-09-13 18:18       ` Johannes Berg
2007-09-14 18:09         ` Dan Williams
2007-09-14 18:25           ` Johannes Berg
2007-09-14 18:33             ` Dan Williams
2007-09-14 18:39               ` Johannes Berg
2007-09-14 19:12           ` dragoran
2007-09-14 20:05             ` Dan Williams
2007-09-14 20:10               ` dragoran [this message]
2007-09-18  0:36       ` Jean Tourrilhes
2007-09-18 10:15         ` Johannes Berg
2007-09-18 17:37           ` Jean Tourrilhes
2007-09-18 19:02             ` Dan Williams
2007-10-16  0:57 ` Jean Tourrilhes
2007-10-16 16:58   ` John W. Linville
2007-10-16 17:29     ` Jean Tourrilhes
2007-10-16 17:39     ` Jean Tourrilhes

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=46EAEAC1.5020105@gmail.com \
    --to=drago01@gmail.com \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=jt@hpl.hp.com \
    --cc=linux-wireless@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).