From: zooko <zooko@zooko•com>
To: Mike Hearn <mike@plan99•net>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>,
Greg Troxel <gdt@work•lexort.com>
Subject: Re: [Bitcoin-development] Linux packaging letter
Date: Wed, 24 Jul 2013 20:01:12 +0400 [thread overview]
Message-ID: <20130724160111.GF1009@zooko.com> (raw)
In-Reply-To: <CANEZrP00vN0TFsxnpSO3RoC_aiAbGS9LG9KXM1+KqWRv8YsJXg@mail.gmail.com>
On Wed, Jul 24, 2013 at 10:28:16AM +0200, Mike Hearn wrote:
> Yeah, if anyone wants to make the letter more digestable please do propose
> an alternative, although by this point it's probably not worth it as people
> have already signed.
Okay, here's my attempt:
https://docs.google.com/document/d/1m3wyBIjqwPQ3wxVT7P_wJtdWt9a9RXvt9NV7rggLAOs/edit#
Please feel free to use any or all of it as you see fit.
> FWIW, Gregory is right that my original draft was much more brusque. The
> pain in the packaging relationship travels both ways. I have in the past
> wasted a lot of time due to bogus packaging applied by non-expert packagers
> that broke things. In fact the project I was a part of adopted a policy of
> automatically closing bug reports from people who were using distributor
> packages (any distro) because the quality was so inconsistent and so many
> subtle bugs were introduced.
>
> If packagers hear upstreams cry about packaging a lot, I think you should
> keep an open mind that some of them probably know what they're talking
> about. We really shouldn't have to beg and cajole here. Saying "we have our
> reasons and we want you to stop" should be enough.
Yes, I know what you mean.
Regards,
Zooko
next prev parent reply other threads:[~2013-07-24 16:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 20:01 Mike Hearn
2013-07-23 20:14 ` Gregory Maxwell
2013-07-23 20:32 ` Mike Hearn
2013-07-23 20:50 ` Gregory Maxwell
2013-07-28 18:21 ` John Dillon
2013-07-23 22:02 ` Scott Howard
2013-07-23 22:26 ` Luke-Jr
2013-07-24 3:00 ` Scott Howard
2013-07-24 1:45 ` Douglas Huff
2013-07-24 2:27 ` Scott Howard
2013-07-24 3:54 ` [Bitcoin-development] Endianness (was: Linux packaging letter) Wendell
2013-07-24 4:03 ` Luke-Jr
2013-07-24 4:07 ` Gregory Maxwell
2013-07-24 4:09 ` Gregory Maxwell
2013-07-23 22:33 ` [Bitcoin-development] Linux packaging letter Pieter Wuille
2013-07-23 23:23 ` Greg Troxel
2013-07-23 23:45 ` Luke-Jr
2013-07-24 0:50 ` Gregory Maxwell
2013-07-24 2:35 ` zooko
2013-07-24 3:19 ` Gregory Maxwell
2013-07-24 8:28 ` Mike Hearn
2013-07-24 13:52 ` Jeff Garzik
2013-07-24 15:32 ` zooko
2013-07-24 19:35 ` Gregory Maxwell
2013-07-24 16:01 ` zooko [this message]
2013-07-27 0:45 ` Greg Troxel
2013-07-27 0:43 ` Greg Troxel
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=20130724160111.GF1009@zooko.com \
--to=zooko@zooko$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=gdt@work$(echo .)lexort.com \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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