Linux CAN drivers development
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Alexander GQ Gerasiov <gq@cs.msu.su>,
	John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: 568303@bugs.debian.org, Markus Becker <mab@comnets.uni-bremen.de>,
	Yegor Yefremov <yegorslists@googlemail.com>,
	linux-can@vger.kernel.org, debian-devel@lists.debian.org
Subject: Re: Bug#568303: can-utils Debian package
Date: Mon, 24 Feb 2014 11:04:20 +0100	[thread overview]
Message-ID: <20140224100420.GE27579@pengutronix.de> (raw)
In-Reply-To: <530B116F.8040203@physik.fu-berlin.de>

Hi Alexander, hi Adrian,

On Mon, Feb 24, 2014 at 10:31:27AM +0100, John Paul Adrian Glaubitz wrote:
> On 02/24/2014 09:59 AM, Alexander GQ Gerasiov wrote:
> > I think you did not get clean with this or that's Uwe who mislead you.
> 
> Yep. I misunderstood Uwe. From his first comments it appeared to me
> that exactly that had happened. So, I apologize to you Alexander
> and take my statements back.
I also apologize to both of you, Alexander and Adrian. I wailed to
Adrian on irc that I'm unhappy with the package as is and bounced some
mails to him. I think I'm the major reason that Adrian got the details
wrong. Sorry. It's not always easy to communicate things properly on
irc, still more when you're peeved.

> > Those commented out overrides were left in rules file from my previous
> > experiments, and not needed anymore. And they have nothing with Uwe's
> > package, I believe.
> 
> Alright, thanks for the explanation.
> 
> > I can count all changes I took from his work:
> > Arch: linux-any (totally forget that SocketCAN is Linux specific)
> > Several strings in description field.
> > 
> > And that's all. =\
> 
> Ok, it appeared to me that the situation was the complete opposite of
> that, i.e. you took Uwe's work and put your name onto it.
That's how it felt to me, but technically that's wrong and most parts
were done by Alexander.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

      reply	other threads:[~2014-02-24 10:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAGm1_ktzQgs92L0RxoVYGVhbb88hZi9dQACF8=pazYHouXh-1w@mail.gmail.com>
     [not found] ` <4947876.WXEsvsyjiy@shelbyville.comnets.uni-bremen.de>
     [not found]   ` <20140115200207.512cf5e8@snail>
     [not found]     ` <20140123183951.GA20892@perseus.defre.xn--kleine-knig-yfb.de>
2014-02-20  9:51       ` Bug#568303: can-utils Debian package Uwe Kleine-König
2014-02-20 13:30         ` Alexander Gerasiov
2014-02-20 14:39           ` Uwe Kleine-König
2014-02-24  6:44           ` Alexander GQ Gerasiov
2014-02-24  7:08             ` John Paul Adrian Glaubitz
2014-02-24  8:25               ` Uwe Kleine-König
2014-02-24  9:18                 ` John Paul Adrian Glaubitz
2014-02-24  8:59               ` Alexander GQ Gerasiov
2014-02-24  9:31                 ` John Paul Adrian Glaubitz
2014-02-24 10:04                   ` Uwe Kleine-König [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=20140224100420.GE27579@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=568303@bugs.debian.org \
    --cc=debian-devel@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=gq@cs.msu.su \
    --cc=linux-can@vger.kernel.org \
    --cc=mab@comnets.uni-bremen.de \
    --cc=yegorslists@googlemail.com \
    /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