From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Alexander GQ Gerasiov <gq@cs.msu.su>,
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 09:25:29 +0100 [thread overview]
Message-ID: <20140224082529.GC27579@pengutronix.de> (raw)
In-Reply-To: <20140224070825.GA31051@physik.fu-berlin.de>
Hi Adrian,
On Mon, Feb 24, 2014 at 08:08:25AM +0100, John Paul Adrian Glaubitz wrote:
> On Mon, Feb 24, 2014 at 10:44:48AM +0400, Alexander GQ Gerasiov wrote:
> > Thu, 20 Feb 2014 17:30:05 +0400
> > Alexander Gerasiov <gq@cs.msu.su> wrote:
> >
> > > Sorry guys. I'm totally busy with other tasks last month :-(. As I
> > > remember your package is quite ready for upload, so I'll do it
> > > tomorrow (without my changes, just add myself as an uploader if you
> > > don't mind). Ok?
> >
> > As Uwe is worried about correctness I'd like to mention, that I did not
> > use his package as the base for last upload, but incorporated some of
> > lines he wrote into my package.
>
> That doesn't sound plausible to me given the fact that you imported
> his debian/rules file and commented out his overrride_dh_* statements
> [1].
>
> If you had incorporated some of his changes, you'd just have use the
> default rules file from the template.
>
> You should also have asked yourself why Uwe had added those overrides
> and not just silently commented them out. If someone adds extra
> overrides, he usually has very good reasons. You should have asked Uwe
> about that.
This is wrong, the overrides are not from me. d/rules seems to be
Alexander's (well, or Joey Hess' and Craig Small's) work.
> > Package is in new queue right now and will be soon available in
> > unstable repository.
>
> It's actually been set to not be reviewed before February 28th to be
> able to discuss this matter first.
I think the best will be when Alexander and I discuss the issue in
private. I don't see a need to pull that conflict into public.
Thanks
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2014-02-24 8:25 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 [this message]
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
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=20140224082529.GC27579@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