From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Issue with the autobuilders: removing 1379 builds from the history?
Date: Tue, 28 May 2013 21:49:21 +0200 [thread overview]
Message-ID: <51A50A41.30103@mind.be> (raw)
In-Reply-To: <20130528214729.6a3669e2@skate>
On 28/05/13 21:47, Thomas Petazzoni wrote:
> Dear Arnout Vandecappelle,
>
> On Tue, 28 May 2013 21:45:40 +0200, Arnout Vandecappelle wrote:
>
>> I would wait a couple of days before removing them. At least for the
>> most recent ones, current HEAD probably still exposes the same problem,
>> so in that sense the build result is still usable.
>
> Ok. I'm not sure they are really usable, but ok.
I usually don't look at the commit ID when reproducing an autobuilder
failure. If I haven't seen a related patch on the list, I'm pretty sure
it will still fail.
>> Would it be possible to direct the URLs to a placeholder page
>> explaining that the build result was removed, so existing links in commit
>> messages don't die?
>
> Yes, I can keep the output directories around, wipe-out their contents,
> and replace it with just a README.txt file that says it has been
> removed and why. Would this be ok for you?
Perfect!
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-05-28 19:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 7:10 [Buildroot] Issue with the autobuilders: removing 1379 builds from the history? Thomas Petazzoni
2013-05-28 7:25 ` Yann E. MORIN
2013-05-28 7:57 ` Peter Korsgaard
2013-05-28 19:45 ` Arnout Vandecappelle
2013-05-28 19:47 ` Thomas Petazzoni
2013-05-28 19:49 ` Arnout Vandecappelle [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=51A50A41.30103@mind.be \
--to=arnout@mind.be \
--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