All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Michael Büsch" <m@bues.ch>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: [PATCH 2/2] b43: implement timeouts workaround
Date: Wed, 11 May 2011 08:06:07 -0500	[thread overview]
Message-ID: <4DCA89BF.8000007@lwfinger.net> (raw)
In-Reply-To: <1305117080.16850.4.camel@maggie>

On 05/11/2011 07:31 AM, Michael B?sch wrote:
> On Wed, 2011-05-11 at 07:17 -0500, Larry Finger wrote:
>> On 05/11/2011 02:35 AM, Rafa? Mi?ecki wrote:
>>> W dniu 11 maja 2011 02:12 u?ytkownik Larry Finger
>>> <Larry.Finger@lwfinger.net>   napisa?:
>>>> On 05/10/2011 06:56 PM, Rafa? Mi?ecki wrote:
>>>>>
>>>>> W dniu 11 maja 2011 01:42 u?ytkownik Larry Finger
>>>>> <Larry.Finger@lwfinger.net>     napisa?:
>>>>>>
>>>>>> On 05/10/2011 07:10 PM, Rafa? Mi?ecki wrote:
>>>>>>>
>>>>>>> Documented in:<4BB81CAD.10602@lwfinger.net>
>>>>>>
>>>>>> This reference is not correct.
>>>>>
>>>>> Ouch, GMail seems to lie to me. Any change you can give me real message id
>>>>> of:
>>>>> http://www.mail-archive.com/b43-dev at lists.infradead.org/msg00049.html
>>>>
>>>> This one is good.
>>>
>>> Sorry, do you mean<4BB81CAD.10602@lwfinger.net>   is OK? Or should I
>>> use link I posted instead of message ID? Or do you know how to get
>>> message ID from the link above?
>>>
>>
>> Use the link
>> "http://www.mail-archive.com/b43-dev at lists.infradead.org/msg00049.html".
>> <4BB81CAD.10602@lwfinger.net>  just points to a non-existent email address on my
>> domain. I don't know how to get a message ID.
>
> It's just an email header added by your MUA.
> For example:   Message-ID:<4DCA7E40.9070709@lwfinger.net>
>
> The advantage of this is that links change and vanish. However, message
> IDs don't. The message ID uniquely identifies a message, regardless of
> where it's stored. So even if the mail archive moves to another URL,
> it's still possible to find the actual mail by the ID.

Ahh. Yes, that Message ID is correct. I just rechecked the header in the mail 
that I sent. Sorry for the confusion and noise.

Larry

WARNING: multiple messages have this Message-ID (diff)
From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Michael Büsch" <m@bues.ch>
Cc: "Rafał Miłecki" <zajec5@gmail.com>,
	linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: Re: [PATCH 2/2] b43: implement timeouts workaround
Date: Wed, 11 May 2011 08:06:07 -0500	[thread overview]
Message-ID: <4DCA89BF.8000007@lwfinger.net> (raw)
In-Reply-To: <1305117080.16850.4.camel@maggie>

On 05/11/2011 07:31 AM, Michael Büsch wrote:
> On Wed, 2011-05-11 at 07:17 -0500, Larry Finger wrote:
>> On 05/11/2011 02:35 AM, Rafał Miłecki wrote:
>>> W dniu 11 maja 2011 02:12 użytkownik Larry Finger
>>> <Larry.Finger@lwfinger.net>   napisał:
>>>> On 05/10/2011 06:56 PM, Rafał Miłecki wrote:
>>>>>
>>>>> W dniu 11 maja 2011 01:42 użytkownik Larry Finger
>>>>> <Larry.Finger@lwfinger.net>     napisał:
>>>>>>
>>>>>> On 05/10/2011 07:10 PM, Rafał Miłecki wrote:
>>>>>>>
>>>>>>> Documented in:<4BB81CAD.10602@lwfinger.net>
>>>>>>
>>>>>> This reference is not correct.
>>>>>
>>>>> Ouch, GMail seems to lie to me. Any change you can give me real message id
>>>>> of:
>>>>> http://www.mail-archive.com/b43-dev@lists.infradead.org/msg00049.html
>>>>
>>>> This one is good.
>>>
>>> Sorry, do you mean<4BB81CAD.10602@lwfinger.net>   is OK? Or should I
>>> use link I posted instead of message ID? Or do you know how to get
>>> message ID from the link above?
>>>
>>
>> Use the link
>> "http://www.mail-archive.com/b43-dev@lists.infradead.org/msg00049.html".
>> <4BB81CAD.10602@lwfinger.net>  just points to a non-existent email address on my
>> domain. I don't know how to get a message ID.
>
> It's just an email header added by your MUA.
> For example:   Message-ID:<4DCA7E40.9070709@lwfinger.net>
>
> The advantage of this is that links change and vanish. However, message
> IDs don't. The message ID uniquely identifies a message, regardless of
> where it's stored. So even if the mail archive moves to another URL,
> it's still possible to find the actual mail by the ID.

Ahh. Yes, that Message ID is correct. I just rechecked the header in the mail 
that I sent. Sorry for the confusion and noise.

Larry

  reply	other threads:[~2011-05-11 13:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11  0:10 [PATCH 1/2] ssb: move ssb_commit_settings and export it Rafał Miłecki
2011-05-11  0:10 ` Rafał Miłecki
2011-05-11  0:10 ` [PATCH 2/2] b43: implement timeouts workaround Rafał Miłecki
2011-05-11  0:10   ` Rafał Miłecki
2011-05-10 23:42   ` Larry Finger
2011-05-10 23:42     ` Larry Finger
2011-05-10 23:56     ` Rafał Miłecki
2011-05-10 23:56       ` Rafał Miłecki
2011-05-11  0:12       ` Larry Finger
2011-05-11  0:12         ` Larry Finger
2011-05-11  7:35         ` Rafał Miłecki
2011-05-11  7:35           ` Rafał Miłecki
2011-05-11 12:17           ` Larry Finger
2011-05-11 12:17             ` Larry Finger
2011-05-11 12:31             ` Michael Büsch
2011-05-11 12:31               ` Michael Büsch
2011-05-11 13:06               ` Larry Finger [this message]
2011-05-11 13:06                 ` Larry Finger

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=4DCA89BF.8000007@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=b43-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=m@bues.ch \
    --cc=zajec5@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.