public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Josh Hunt <joshhunt00@gmail.com>
Cc: Michal Marek <mmarek@suse.cz>, Joerg Roedel <joro@8bytes.org>,
	linux-kbuild@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Borislav Petkov <bp@suse.de>
Subject: Re: [PATCH] buildtar: Add ARCH to the archive name
Date: Thu, 12 Sep 2013 14:46:02 +0200	[thread overview]
Message-ID: <20130912124602.GA9280@x1.alien8.de> (raw)
In-Reply-To: <CAKA=qzZRfSD33u4cXvpnzQn5isNB4iNY4cibeAwY46gyFmMHhg@mail.gmail.com>

On Wed, Sep 11, 2013 at 06:35:08PM -0500, Josh Hunt wrote:
> I didn't take the time to build the rpm pkg, but deb-pkg produces files
> like:
> 
> linux-image-3.10.0-rc7_3.10.0-rc7-26_amd64.deb
> 
> tarbz2-pkg now produces files with the name of:
> linux-3.10.0-rc7-x86.tar.bz2

Right, I'm not really happy with this solution too because builds which
don't supply ARCH on the command line add "x86" to the archive name
and my intention was to have either "i386" or "x86_64" appended to the
archive name so that when building a bunch of different kernel packages,
I can know which is 32-bit and which is 64-bit.

Having it say "x86" doesn't tell me all that much. Whether it has "-" or
an "_" prepended I don't care.

So I'll go and revisit this thing. I'll add you to CC for feedback since
your script got broke :)

And, btw, other suggestions are appreciated too.

Thanks.

-- 
Regards/Gruss,
Boris.

      parent reply	other threads:[~2013-09-12 12:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-06  8:05 [PATCH] buildtar: Add ARCH to the archive name Borislav Petkov
2013-03-07 11:06 ` Joerg Roedel
2013-03-07 11:09   ` Borislav Petkov
2013-04-08 14:05     ` Michal Marek
2013-04-08 14:26       ` Borislav Petkov
     [not found]         ` <CAKA=qzZRfSD33u4cXvpnzQn5isNB4iNY4cibeAwY46gyFmMHhg@mail.gmail.com>
2013-09-12 12:46           ` Borislav Petkov [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=20130912124602.GA9280@x1.alien8.de \
    --to=bp@alien8.de \
    --cc=bp@suse.de \
    --cc=joro@8bytes.org \
    --cc=joshhunt00@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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