All of lore.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:32:36 +0200	[thread overview]
Message-ID: <20090401173236.GZ3901@baikonur.stro.at> (raw)
In-Reply-To: <200904011907.31585.elendil@planet.nl>

On Wed, Apr 01, 2009 at 07:07:29PM +0200, Frans Pop wrote:
> On Wednesday 01 April 2009, maximilian attems wrote:
> > Sam can you please merge 1-6 of the series as those are not contested.
> > thanks.
> 
> I continue to object to patch 4.

your objection on patch 4 is disregarded.
 
> > the patches were submitted to the relevant subsystem,
> > no need to flood lkml with such.
> 
> However, they are also patches with a fairly general impact that should be 
> reviewed by more people than just the narrow group that is subscribed to 
> kbuild. lkml is the generic list and is often CCed in such cases. AFAIK 
> most kbuild patches go through lkml.
> It's just chance that I saw these and was able to comment.

come on, i pointed out this thread to you.
it is enough to post to relevant maintainer list.
subscribe to linux-fs if you interested in vfs changes and so on..
 
> > > [PATCH 4/7] deb-pkg: Fix Section and Source field
> > >             http://marc.info/?l=linux-kbuild&m=123851275123210&w=2
> > >
> > > I strongly disagree with this patch.
> > >
> > > linux-2.6 is the source package for official Debian kernels and
> > > packages built using deb-pkg are NOT built from that source package.
> > > IMO there's no need to change it (the field is required and thus
> > > cannot simply be dropped). If it does want changing for some reason
> > > I'd suggest "linux-upstream" or similar.
> >
> > no,
> > just checkout linux-2.6 git and you'll get per default a matching
> > linux-2.6 dir, so your arg does not stand.
> 
> That still does not change the fact that when I build directly from git 
> head or whatever other git branch or downloaded upstream source the 
> binary package is *not* built from the linux-2.6 source package.
> 
> Therefore setting source to linux-2.6 is factually incorrect.

no it is not more incorrect then setting to linux.
we don't care about corner cases, but go for the general one:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
cd linux-2.6
make <config>
make deb-pkg

it does *not* matter that linux-2.6 happens to be same name
than the debian linux images source package.
 
[ snipping discussion of patch 7 that will get reworked ]

-- 
maks

  reply	other threads:[~2009-04-01 17:35 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 [this message]
2009-04-01 17:53       ` Frans Pop
2009-04-01 17:57         ` maximilian attems
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=20090401173236.GZ3901@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.