[arch-dev-public] [PATCH] initscripts: Add a splash support

Jason Chu jason at archlinux.org
Sun Nov 4 15:48:35 EST 2007

On Sun, Nov 04, 2007 at 02:10:28PM +0100, Daniel Isenmann wrote:
> On Sun, 04 Nov 2007 13:37:26 +0100
> Thomas Bächler <thomas at archlinux.org> wrote:
> > So, despite the fact that I am willing to listen to the concerns
> > of others, the final decision lies with me and tpowa.
> > 
> Then the whole discussion is senseless. It's like we have concerns
> about it, but you do what you want, because you are maintaining it.
> You are doing a great job on initscripts, that's clear. But the
> behaviour isn't ok! Just opening a branch that CAN be merged later
> despite the concerns of others isn't right. I know, you can delete this
> branch, if it isn't merged later, but I think we are a team and have
> discuss and decide several things together.
> Sorry for my words, if they sounds a little bit aggressive....

I'm going to jump on this bandwagon for a minute...

I just read your concern and it was "I dislike the idea to make it more
complex just for eyecandy".  Do you or have you ever maintained
initscripts?  Have you ever submitted a patch or fixed a bug to do with
them?  If not, then why does it matter how complex something gets if it
just works for what you need it to do?

The people who do maintain it and fix the bugs *do* want the patch.  Who
are you to say whether it's too complex for them or not?  Why not say,
"thank you for writing the patch, I'm sure that lots of people will be very
happy that things have become easier for them"?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://archlinux.org/pipermail/arch-dev-public/attachments/20071104/3cb317f2/attachment.pgp>

More information about the arch-dev-public mailing list