public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Bruce Cran <bruce@cran.org.uk>, Andrew Fish <afish@apple.com>
Cc: edk2-devel-01 <edk2-devel@ml01.01.org>
Subject: Re: Ingebrigtsen: The End of Gmane?
Date: Mon, 1 Aug 2016 15:25:15 +0200	[thread overview]
Message-ID: <27de671e-1a95-3f6b-f48f-52d32fa53d83@redhat.com> (raw)
In-Reply-To: <c2e8a143-0553-a8fc-214e-784801f6d9b5@cran.org.uk>

On 07/31/16 04:25, Bruce Cran wrote:
> On 7/28/2016 1:19 PM, Andrew Fish wrote:
> 
>> Seems he will send you the disks. What could go wrong?
> 
> I'm actually tempted to take him up on that offer.
> Just today I went looking for information about UefiDebugLib to see if
> it was possible for a driver to print debug information to the serial
> port (or other sort of debug device) instead of the console, and came
> across the thread at
> http://comments.gmane.org/gmane.comp.bios.tianocore.devel/3024 where
> thanks to Google's cache I learned that:
> 
> "The EDK used some Tiano and implementation defined protocols to support
> DEBUG and ASSERT macros. So DEBUG
> and ASSERT from the EDK can only be reliably used if you compile all the
> EDK firmware together. As Liming
> points out it is much safer to use a UEFI console based debug message
> for developing generic drivers and
> applications."
> 
> It's a shame to lose information like that.

I think the Internet Archive intends to pick up the DB + WebUI:

https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/comment-page-1/#comment-13501

Also, from Lars Ingebrigtsen (speaking to a yet to be determined entity):

"I hand over the gmane.org domain to you [...] All previous
permalink.gmane.org (etc.) links continue to work as before, but they’ll
look new and spiffy in your new and spiffy web interface."

https://lars.ingebrigtsen.no/2016/07/28/the-end-of-gmane/comment-page-1/#comment-13502

(Actually, I'm a huge fan of the current (oldie but goldie) WebUI, so
"new and spiffy" is a minus for me, but at least the links should
continue to work.)

Going forward I'll have to constrain myself to the builtin mailman2
links at <https://lists.01.org/pipermail/edk2-devel/>. (Thanks again
Bruce and Mike for enabling those.)

Thanks
Laszlo


  reply	other threads:[~2016-08-01 13:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <44fc515a-ce09-f8d0-88e3-ea665f34a11f@redhat.com>
     [not found] ` <46d85e1f-cf83-55cb-6b7a-46dbbe226f83@cran.org.uk>
2016-07-29  0:46   ` Ingebrigtsen: The End of Gmane? Kinney, Michael D
2016-07-29  4:07     ` Bruce Cran
2016-07-29  7:44       ` Laszlo Ersek
     [not found] ` <85D48248-620C-4675-A090-C47C68ABC145@apple.com>
2016-07-31  2:25   ` Bruce Cran
2016-08-01 13:25     ` Laszlo Ersek [this message]
2016-09-05 17:51       ` Rafael Machado
2016-09-06  9:25         ` Laszlo Ersek
2016-09-06 11:08           ` Rafael Machado
2016-09-06 16:20           ` Bruce Cran
2016-09-06 19:39             ` Rafael Machado
2016-09-19 11:23             ` Laszlo Ersek

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-list 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=27de671e-1a95-3f6b-f48f-52d32fa53d83@redhat.com \
    --to=devel@edk2.groups.io \
    /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