From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-libs/mlt: ChangeLog mlt-0.5.4-r1.ebuild
Date: Sat, 14 Aug 2010 17:29:44 +0300 [thread overview]
Message-ID: <20100814142944.GA15913@Mystical> (raw)
In-Reply-To: <201008141720.39003.aballier@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1544 bytes --]
On Sat, Aug 14, 2010 at 05:20:38PM +0300, Alexis Ballier wrote:
> On Saturday 14 August 2010 17:00:38 Markos Chandras wrote:
> [...]
> > > > > - There is absolutely no reference to any patch sent upstream and I
> > > > > have not seen anything on the upstream dev ml.
> > > >
> > > > Thats because I didn't. I've fixed more than 40 bug wrt LDFLAGS. Do you
> > > > expect me to subscribe to 40 different ML and send them upstream?
> > >
> > > you don't need to subscribe, there's usually an AUTHORS file with emails
> > > you can use...
> >
> > As I said, I thought that maintainers was responsible to do it since they
> > follow all the bug progress after all. So according to you I should do all
> > the work. Tempting
>
> yes please; I consider not doing it a bit rude as the maintainers will _have_
> to clean after you.
So do I. Fixing your package and you don't even bother to send a *ready to go* patch
upstream seems like a bit rude to me as well. Perhaps, we do have a complete
different point of view in this one.
Recent example is Chí-Thanh Christopher Nguyễn who thanked me for fixing his
package, asked me to attach the patch so *he* can send it upstream. I thought
that was the *default* policy. Anyway. I should talk to each maintainer
separately when I fix his package. Seems to me is the best approach
>[...]
> A.
>
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-14 14:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100806212139.9E8422CE15@corvid.gentoo.org>
2010-08-14 12:35 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in media-libs/mlt: ChangeLog mlt-0.5.4-r1.ebuild Alexis Ballier
2010-08-14 12:50 ` Markos Chandras
2010-08-14 13:10 ` Alex Alexander
2010-08-14 13:47 ` Markos Chandras
2010-08-14 16:16 ` Alex Alexander
2010-08-14 17:00 ` Markos Chandras
2010-08-14 17:21 ` Alex Alexander
2010-08-14 17:34 ` Markos Chandras
2010-08-14 17:43 ` Alex Alexander
2010-08-14 18:35 ` Duncan
2010-08-14 18:51 ` Richard Freeman
2010-08-14 22:00 ` Dale
2010-08-14 16:26 ` Thilo Bangert
2010-08-14 17:06 ` Markos Chandras
2010-08-16 11:31 ` Peter Volkov
2010-08-14 17:35 ` Harald van Dijk
2010-08-14 20:31 ` Ryan Hill
2010-08-15 8:13 ` Thomas Sachau
2010-08-14 13:37 ` Alexis Ballier
2010-08-14 14:00 ` Markos Chandras
2010-08-14 14:20 ` Alexis Ballier
2010-08-14 14:29 ` Markos Chandras [this message]
2010-08-14 16:08 ` Richard Freeman
2010-08-14 16:19 ` Thilo Bangert
2010-08-14 20:46 ` Ryan Hill
2010-08-14 20:55 ` Markos Chandras
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=20100814142944.GA15913@Mystical \
--to=hwoarang@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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