From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH 2/3] download/git: recover dirty cache
Date: Tue, 17 Apr 2018 12:42:13 +0200 [thread overview]
Message-ID: <20180417104213.GB8142@scaer> (raw)
In-Reply-To: <1ffe206e-4b1e-c233-a511-ba4c3a8cb5f0@armadeus.com>
Julien, All,
On 2018-04-17 12:05 +0200, Julien Boibessot spake thusly:
> On 16/04/2018 22:56, Yann E. MORIN wrote:
>
> Ricardo, All,To all autobuilder runners: could you create a tarball of the failed
> dtv-scan-tables git tree on yuour autobuilders, from each of your
> instances, please?
>
> I'm not sure to understand what you reallly need, could you please clarify ?
You are running an autobuilder. That autobuilder will run 'n' builds in
parallel, each in a directory instance-0, instance-1... In each of those
instances, there is a dl/ sub-dir.
In that dl/ sub-dir, there isyet another sub-dir per-package, of which
dtv-scan-tables/
Buildroot downloads dtv-scan-tables as a git clone, stored in the git/
directory of the aforementioned dtv-scan-tables/ directory.
I would need that you provide all thos git trees from all the instances
your autobuilder runs, i.e. something like:
tar cJf dtv-scan-tables-git.tar.xz instance-*/dl/dtv-scan-tables/git/
And then send me dtv-scan-tables-git.tar.xz
Please! ;-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2018-04-17 10:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-12 9:28 [Buildroot] [RFC PATCH 0/3] fix some corner cases for download/git v1 Ricardo Martincoski
2018-04-12 9:28 ` [Buildroot] [RFC PATCH 1/3] download/git: fix fetch all refs for old git Ricardo Martincoski
2018-04-12 17:42 ` Yann E. MORIN
2018-04-13 18:23 ` Ricardo Martincoski
2018-04-15 12:12 ` Yann E. MORIN
2018-04-16 2:17 ` Ricardo Martincoski
2018-04-12 9:28 ` [Buildroot] [RFC PATCH 2/3] download/git: recover dirty cache Ricardo Martincoski
2018-04-12 17:48 ` Yann E. MORIN
2018-04-13 18:28 ` Ricardo Martincoski
2018-04-15 12:02 ` Yann E. MORIN
2018-04-16 2:54 ` Ricardo Martincoski
2018-04-16 16:01 ` Yann E. MORIN
2018-04-16 20:56 ` Yann E. MORIN
[not found] ` <1ffe206e-4b1e-c233-a511-ba4c3a8cb5f0@armadeus.com>
2018-04-17 10:42 ` Yann E. MORIN [this message]
2018-04-17 11:30 ` Thomas Petazzoni
2018-04-17 4:45 ` Ricardo Martincoski
2018-04-17 7:04 ` Ricardo Martincoski
2018-04-17 8:10 ` Arnout Vandecappelle
2018-04-17 8:56 ` Ricardo Martincoski
2018-04-17 10:36 ` Yann E. MORIN
2018-04-17 11:58 ` Arnout Vandecappelle
2018-04-12 9:28 ` [Buildroot] [RFC PATCH 3/3] download/git: unshallow when fetching all refs Ricardo Martincoski
2018-04-12 11:28 ` Thomas Petazzoni
2018-04-12 17:33 ` Yann E. MORIN
2018-04-13 18:32 ` Ricardo Martincoski
2018-04-15 12:08 ` Yann E. MORIN
2018-04-16 3:04 ` Ricardo Martincoski
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=20180417104213.GB8142@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/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