public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: maximilian attems <max@stro.at>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kbuild@vger.kernel.org,
	Andres Salomon <dilinger@debian.org>,
	tytso@mit.edu, sam@ravnborg.org
Subject: Re: Comments on deb-pkg patch series
Date: Wed, 1 Apr 2009 19:57:33 +0200	[thread overview]
Message-ID: <20090401175733.GA3901@baikonur.stro.at> (raw)
In-Reply-To: <200904011953.53889.elendil@planet.nl>

On Wed, Apr 01, 2009 at 07:53:52PM +0200, Frans Pop wrote:
> On Wednesday 01 April 2009, maximilian attems wrote:
> > > I continue to object to patch 4.
> >
> > your objection on patch 4 is disregarded.
> 
> Eh, sorry, but that's not up to you. It's fine that you disagree with me. 
> But as you're not the owner or primary maintainer of the builddeb script, 
> you don't get to "disregard" comments from anybody.
> 
> I'm happy to let Sam decide on this based on the given arguments. Maybe 
> others will comment too.

no
on patch 7 you had a technical reason,
thus i agree with you that this needs better thought or work.
 
> > it does *not* matter that linux-2.6 happens to be same name
> > than the debian linux images source package.
> 
> Technically it does not matter, correct. But for the same reason there is 
> also no good reason to make it the same as the debian linux images source 
> package.
> 
> And as it is factually incorrect I still don't like it. It would very 
> simply result in incorrect info if people query their system using tools 
> like grep-dpkg, or even if they just just view the package info.

we in the Debian kernel team use linux-2.6 as we use the linux-2.6 git
tree as upstream, as it happens to be the primary upstream. so i still
miss your point why make deb-pkg shouldn't show that too!

btw this patch also fixes wrong section behaviour of make deb-pkg.


  reply	other threads:[~2009-04-01 18:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-01 16:07 Comments on deb-pkg patch series Frans Pop
2009-04-01 16:23 ` maximilian attems
2009-04-01 17:07   ` Frans Pop
2009-04-01 17:32     ` maximilian attems
2009-04-01 17:53       ` Frans Pop
2009-04-01 17:57         ` maximilian attems [this message]
2009-04-01 18:35           ` Frans Pop
2009-04-01 18:47             ` maximilian attems
2009-04-01 19:11               ` Frans Pop
2009-04-01 19:21                 ` maximilian attems
2009-04-05 19:38   ` Sam Ravnborg

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=20090401175733.GA3901@baikonur.stro.at \
    --to=max@stro.at \
    --cc=dilinger@debian.org \
    --cc=elendil@planet.nl \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=tytso@mit.edu \
    /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