public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
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 23:55:16 +0300	[thread overview]
Message-ID: <20100814205516.GA18939@Mystical> (raw)
In-Reply-To: <20100814144621.4b4169f7@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]

On Sat, Aug 14, 2010 at 02:46:21PM -0600, Ryan Hill wrote:
> On Sat, 14 Aug 2010 17:00:38 +0300
> Markos Chandras <hwoarang@gentoo.org> wrote:
> 
> > > 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
> 
> When you take on the task of fixing a bug in a package you don't maintain,
> you are responsible for the whole task, not just the part you want to do.
> You essentially become the maintainer for that change.  So just do what you
> would do if it really was your package.
> 
> And really I don't care if you upstream the patch or not, but when the
> maintainer politely asks you to do so the correct response is "okay", not "do
> it yourself".
> 
> 
> -- 
> fonts, gcc-porting,                                   and it's all by design
> toolchain, wxwidgets                        to keep us from losing our minds
> @ gentoo.org                EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

You misunderstood me. I never said "do it yourself". I said that I didn't know
that I have to do it myself and that I will do it from now on

-- 
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 --]

      reply	other threads:[~2010-08-14 20:53 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
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 [this message]

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=20100814205516.GA18939@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