From: Yves-Alexis Perez <corsac@debian.org>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] builddeb: generate a changes file from the build
Date: Sat, 16 May 2015 11:43:49 +0200 [thread overview]
Message-ID: <1431769429.14305.29.camel@debian.org> (raw)
In-Reply-To: <1431606908-20880-1-git-send-email-corsac@debian.org>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
On jeu., 2015-05-14 at 14:35 +0200, Yves-Alexis Perez wrote:
> +# Generate a change file
> +(cd $KBUILD_OUTPUT; dpkg-genchanges -b > ../linux_${packageversion}_${debarch}.changes)
> +
Actually cwd during the build is KBUILD_OUTPUT already, so the cd part
is unnecessary (I can resend a v2 if really needed).
Regards,
--
Yves-Alexis
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-05-16 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 12:35 [PATCH] builddeb: generate a changes file from the build Yves-Alexis Perez
2015-05-16 9:43 ` Yves-Alexis Perez [this message]
2015-05-28 9:50 ` Riku Voipio
2015-05-28 11:26 ` Yves-Alexis Perez
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=1431769429.14305.29.camel@debian.org \
--to=corsac@debian.org \
--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;
as well as URLs for NNTP newsgroup(s).