Re: maintainer communication
On Mon, Dec 23, 2013 at 22:14:00 +, Thorsten Glaser wrote: > My intent in _this_ thread was to get a discussion among > debian-ports.org users started for best practices of how > to communicate with package maintainers in Debian. Sorry > for being unclear there. I had hoped for hints ☺ since I > know my communication skills lack somewhat. > debian-po...@lists.debian.org is an alias for *all* debian-$arch lists for debian architectures. It has nothing to do with debian-ports.org. If you want a list for debian-ports.org users go create one, but please don't abuse this one. Thanks, Julien signature.asc Description: Digital signature
Re: maintainer communication
On Mon, Dec 23, 2013 at 10:59 PM, Finn Thain wrote:
>> >Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was
>>
>> See the discussion in the thread before this message.
>
> I've seen no discussion of this on debian-68k or linux-m68k. What
> discussion are you referring to?
>
> The subject of this thread (before you shortened it) was "maintainer
> communication (was Re: Debian kernel regression, was Re: Modernizing a
> Macintosh LC III)".
>
> That discussion covered both the usefulness of the serial console (i.e.
> CONFIG_SERIAL_PMACZILOG) and the problematic disappearance of
> CONFIG_EARLY_PRINTK.
I guess it's about the crash on non-Mac when passing debug=serial.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CAMuHMdVDH9Jw979gU=+GVCdwXzDFww+tNFY=pmd4fkpmfaq...@mail.gmail.com
Re: maintainer communication
Michael Banck dixit:
>I am not sure which thread you are meaning, and in general, I think
>discussing random Linux kernel config options on -ports is off-topic.
Indeed, that wasn’t the intent of this thread. I’ve continued
that particular discussion on debian-68k.
My intent in _this_ thread was to get a discussion among
debian-ports.org users started for best practices of how
to communicate with package maintainers in Debian. Sorry
for being unclear there. I had hoped for hints ☺ since I
know my communication skills lack somewhat.
bye,
//mirabilos
--
> emacs als auch vi zum Kotzen finde (joe rules) und pine für den einzig
> bedienbaren textmode-mailclient halte (und ich hab sie alle ausprobiert). ;)
Hallo, ich bin der Holger ("Hallo Holger!"), und ich bin ebenfalls
... pine-User, und das auch noch gewohnheitsmäßig ("Oooohhh"). [aus dasr]
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/pine.bsm.4.64l.1312232212380.2...@herc.mirbsd.org
Re: maintainer communication
On Mon, 23 Dec 2013, Thorsten Glaser wrote: > Finn Thain dixit: > > >Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was > > See the discussion in the thread before this message. I've seen no discussion of this on debian-68k or linux-m68k. What discussion are you referring to? The subject of this thread (before you shortened it) was "maintainer communication (was Re: Debian kernel regression, was Re: Modernizing a Macintosh LC III)". That discussion covered both the usefulness of the serial console (i.e. CONFIG_SERIAL_PMACZILOG) and the problematic disappearance of CONFIG_EARLY_PRINTK. > > >CONFIG_EARLY_PRINTK disabled? > > It was never enabled. Yes it was. See "Modernizing a Macintosh LC III": http://lists.debian.org/debian-68k/2013/11/msg00070.html Finn -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.LNX.2.00.1312240849320.18824@nippy.intranet
Re: maintainer communication
Hi, On Mon, Dec 23, 2013 at 04:47:30PM +, Thorsten Glaser wrote: > Finn Thain dixit: > > >Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was > > See the discussion in the thread before this message. I am not sure which thread you are meaning, and in general, I think discussing random Linux kernel config options on -ports is off-topic. Maybe you sent the initial mail to the wrong list? Michael -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131223170941.gg4...@raptor.chemicalconnection.dyndns.org
Re: maintainer communication
Finn Thain dixit: >Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was See the discussion in the thread before this message. >CONFIG_EARLY_PRINTK disabled? It was never enabled. And that’s what you get when you let a BSD guy whose Linux experience dates back to 2.0.3[3-6] (and some 2.4.3) do the Debian/m68k Linux kernel config, instead of someone who actually knows about this. I did warn y’all back then. Now we got a config, and we can incrementally improve it. >how it can help when it is downstream of the kernel developers. Eh? Parse error. bye, //mirabilos -- „Also irgendwie hast du IMMER recht. Hier zuckelte gerade ein Triebwagen mit der Aufschrift "Ostdeutsche Eisenbahn" durch Wuppertal. Ich glaubs machmal nicht…“ -- Natureshadow, per SMS „Hilf mir mal grad beim Denken“ -- Natureshadow, IRL, 2x -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1312231645470.2...@herc.mirbsd.org
Re: maintainer communication (was Re: Debian kernel regression, was Re: Modernizing a Macintosh LC III)
On Mon, 23 Dec 2013, Thorsten Glaser wrote: > > CONFIG_EARLY_PRINTK=y and CONFIG_SERIAL_PMACZILOG=n Why is CONFIG_SERIAL_PMACZILOG to be disabled? And why was CONFIG_EARLY_PRINTK disabled? > I think we need to file bugs in the BTS for each of these instances in > the future, instead of trying to communicate with the maintainers > directly. Sure, if the BTS process would help avoid these mistakes. But I don't see how it can help when it is downstream of the kernel developers. Finn -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/alpine.LNX.2.00.1312232231090.18343@nippy.intranet
maintainer communication (was Re: Debian kernel regression, was Re: Modernizing a Macintosh LC III)
Dixi quod… >Hi $maintainer, > >can we still get CONFIG_EARLY_PRINTK=y and >CONFIG_SERIAL_PMACZILOG=n into 3.12 before it hits unstable? This was, of course, not integrated into src:linux before the 3.12.6-1 upload. (Which by the way autobuilt, meaning we have build logs ☻ instead of me building it in cowbuilder manually on a – possibly faster – VM.) The request to the GCC maintainer to somehow make autoconf regenerate some more configure scripts, to fix the -fpic/-fPIC problem, was, of course, also not integrated. I think we need to file bugs in the BTS for each of these instances in the future, instead of trying to communicate with the maintainers directly. I hate it, because I like to talk to humans more, and some people on the Debian side hate it too (“because debports is not Debian”), but… *shrug*. Tell me if you have a better idea. Or anything else to comment on this matter. To clarify: this is *not* intended to make package maintainers show in a bad light, rather the contrary, trying to improve things. I can understand that things that are not in the BTS are likely to be forgotten (in fact I forgot a suggestion how to do/fix something too, due to falling ill last week and not writing it down e.g. in the bug). Thanks, //mira“still on antibiotics but recovering”bilos -- Beware of ritual lest you forget the meaning behind it. yeah but it means if you really care about something, don't ritualise it, or you will lose it. don't fetishise it, don't obsess. or you'll forget why you love it in the first place. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1312231011210.24...@herc.mirbsd.org
