public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: qa <qa@gentoo.org>, comrel@gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: net-libs/libssh2/
Date: Mon, 01 Oct 2018 23:43:06 +0200	[thread overview]
Message-ID: <1538430186.1095.40.camel@gentoo.org> (raw)
In-Reply-To: <20181001231303.0386d024@wim.jer>

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

On Mon, 2018-10-01 at 23:13 +0200, Jeroen Roovers wrote:
> On Mon, 01 Oct 2018 17:00:24 +0200
> Michał Górny <mgorny@gentoo.org> wrote:
> 
> > On Mon, 2018-10-01 at 11:46 +0000, Jeroen Roovers wrote:
> > > commit:     d866d4705e1e4a092579a31df2815e3407950a19
> > > Author:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
> > > AuthorDate: Mon Oct  1 11:45:43 2018 +0000
> > > Commit:     Jeroen Roovers <jer <AT> gentoo <DOT> org>
> > > CommitDate: Mon Oct  1 11:46:10 2018 +0000
> > > URL:
> > > https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d866d470
> > > 
> > > net-libs/libssh2: Add USE=mbedtls, switch to cmake for building
> > > 
> > > * Add support for net-libs/mbedtls
> > > * Switch to cmake as the autotools build is even more broken
> > > * Remove USE=static-libs as that inhibits building shared libs
> > > * Use REQUIRED_USE to force choosing a crypto backend
> 
> You completely skipped over the improvements. In effect, you show
> yourself to be completely unresponsive to what were considered positive
> changes to the author of the work.
> 
> Then you begin to pick apart what you think is wrong. It's not obvious
> why you are doing it this way, and with regard to practically all
> of your earlier e-mails addressed to me, I can only assume malice.

I'm sorry but I'm not going to help you if you keep attacking me like
this.  I have merely pointed out mistakes I've noticed.  I did it
privately specifically with respect to you.  You turn this into some
kind of public slandering effort, apparently for no other reason than
'assuming malice'.

I'm sorry if you can't see anything good in people.  When someone points
out an issue with my ebuild, I assume he just wants to have the ebuild
improved.  But now I learn people do that out of sheer malice.

I'm sorry that my comments were not detailed enough.  I have wrongly
assumed they'd point you in the right direction, and you'd be able to
solve those issues with help of eclass documentation.

> Someone suggested in an e-mail that "he is just annoyed that you broke
> an ebuild that he has spent some time maintaining", but `git shortlog
> -- .` would tell you quite a different story. What I think is happening
> here is that you think I am "touching your stuff". You have to nitpick
> at it instead of just fixing it together and then sending me an update
> about the extra work or by pointing out the problems in a more humane
> way and leaving me to fix them.

That's one way to look at it.  The other way is that you're so horribly
abrasive that I'm *scared* to touch this ebuild beyond what needs to be
absolutely done.  That's why I didn't switch it to CMake earlier --
because I presumed you'd attack me again.  It seems I wasn't wrong after
all.

-- 
Best regards,
Michał Górny

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 963 bytes --]

      reply	other threads:[~2018-10-01 21:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1538394370.d866d4705e1e4a092579a31df2815e3407950a19.jer@gentoo>
     [not found] ` <1538406024.1095.4.camel@gentoo.org>
2018-10-01 19:30   ` [gentoo-dev] Re: [gentoo-commits] repo/gentoo:master commit in: net-libs/libssh2/ Jeroen Roovers
2018-10-01 19:41     ` Michał Górny
2018-10-01 20:04     ` Michał Górny
2018-10-01 21:13   ` Jeroen Roovers
2018-10-01 21:43     ` Michał Górny [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=1538430186.1095.40.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=comrel@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=qa@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