From: "Alm, Michael" <Michael.Alm@elac-wartsila.de>
To: "'ptxdist@pengutronix.de'" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Yocto
Date: Fri, 15 Sep 2017 11:02:14 +0000 [thread overview]
Message-ID: <7b6d6988778445bb859b1851cedfb4f1@elac-wartsila.de> (raw)
In-Reply-To: <20170915064707.qowgefziguuelntx@pengutronix.de>
Hi,
when was the -j option added to ptxdist? Which version?
Regards,
Michael
-----Ursprüngliche Nachricht-----
Von: ptxdist [mailto:ptxdist-bounces@pengutronix.de] Im Auftrag von Michael Olbrich
Gesendet: Freitag, 15. September 2017 08:47
An: ptxdist@pengutronix.de
Betreff: Re: [ptxdist] Yocto
Hi,
On Fri, Sep 15, 2017 at 12:44:13AM +0200, Tim Sander wrote:
> Am Mittwoch, 13. September 2017, 17:38:24 CEST schrieb Michael Olbrich:
> > Btw. don't use '-jeX -jiX' use '-j' instead. That uses a global
> > jobserver shared by all packages.
> Well i missed out this one. I know that this option didn't exist. But
> i didn't realize that its now the recommended way. Its much better
> now, just with a few passages where the cores are waiting for install io.
>
> Probably you should update the default output of ptxdist. Because at
> least
> 2017.07.0 doesn't list -j as an option. So now i know why the -j
> options slipped my attention :-).
I added it to the documentation but not the help text :-/. Fixed now.
> Besides what is -je good for now?
Nothing really. I left it there at first because I wasn't sure if there were any problems with -j. Now it's just for backwards compatibility.
Regards,
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-09-15 11:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-09 13:03 Erwin Rol
2017-09-09 15:54 ` Enrico Weigelt, metux IT consult
2017-09-09 16:33 ` Erwin Rol
2017-09-10 19:24 ` Enrico Weigelt, metux IT consult
2017-09-10 20:09 ` Erwin Rol
2017-09-09 18:36 ` Tim Sander
2017-09-10 19:16 ` Robert Schwebel
2017-09-12 18:42 ` Tim Sander
2017-09-12 20:12 ` Robert Schwebel
2017-09-12 21:33 ` Tim Sander
2017-09-13 5:42 ` Robert Schwebel
2017-09-13 15:38 ` Michael Olbrich
2017-09-14 22:44 ` Tim Sander
2017-09-15 6:47 ` Michael Olbrich
2017-09-15 11:02 ` Alm, Michael [this message]
2017-09-16 9:25 ` Michael Olbrich
2017-09-10 19:13 ` Robert Schwebel
2017-09-11 9:25 ` Guillermo Rodriguez Garcia
2017-09-12 10:49 ` Alexander Dahl
[not found] <20170911063001.A6FE73EC2A2E_9B62D69B@mail.eckelmann.de>
2017-09-11 7:14 ` Schenk, Gavin
2017-09-12 10:44 ` Alexander Dahl
2017-09-12 13:29 ` Schenk, Gavin
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=7b6d6988778445bb859b1851cedfb4f1@elac-wartsila.de \
--to=michael.alm@elac-wartsila.de \
--cc=ptxdist@pengutronix.de \
/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