From: "Frank Ch. Eigler" <fche@elastic.org>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: Mark Wielaard <mark@klomp.org>,
buildbot@sourceware.org, binutils@sourceware.org,
Nick Clifton <nickc@redhat.com>,
elena.zannoni@oracle.com, david.faust@oracle.com
Subject: Re: binutils snapshot builds
Date: Thu, 23 May 2024 11:28:38 -0400 [thread overview]
Message-ID: <Zk9gpuOCL0BpZZLy@elastic.org> (raw)
In-Reply-To: <87y180mukz.fsf@oracle.com>
Hi -
> binutils-2.42.50.tar.gz
> What about having:
> binutils-2.42.50-fc12b44ec0e.tar.gz
(Or else: git-describe.)
> This would allow for example to easily cache already downloaded
> snapshots on the client side.
By the way .... could someone spell out in what way these source
tarball snapshots are useful, when the git repo is already easily
available?
- FChE
next prev parent reply other threads:[~2024-05-23 15:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 22:08 Mark Wielaard
2024-05-22 22:08 ` [PATCH 1/2] Add binutils-snapshots builder Mark Wielaard
2024-05-22 22:08 ` [PATCH 2/2] binutils snapshot steps should run in the git step workdir Mark Wielaard
2024-05-23 10:35 ` binutils snapshot builds Nick Clifton
2024-05-23 23:32 ` Mark Wielaard
2024-05-24 12:31 ` Nick Clifton
2024-05-24 14:03 ` Jose E. Marchesi
2024-05-23 15:11 ` Jose E. Marchesi
2024-05-23 15:28 ` Frank Ch. Eigler [this message]
2024-05-23 15:33 ` Jose E. Marchesi
2024-05-23 22:52 ` Sam James
2024-05-23 23:59 ` Mark Wielaard
2024-05-23 23:41 ` Mark Wielaard
2024-05-24 9:58 ` Jose E. Marchesi
2024-05-26 0:16 ` Mark Wielaard
2024-05-28 14:35 ` Nick Clifton
2024-05-28 16:16 ` Mark Wielaard
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=Zk9gpuOCL0BpZZLy@elastic.org \
--to=fche@elastic.org \
--cc=binutils@sourceware.org \
--cc=buildbot@sourceware.org \
--cc=david.faust@oracle.com \
--cc=elena.zannoni@oracle.com \
--cc=jose.marchesi@oracle.com \
--cc=mark@klomp.org \
--cc=nickc@redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).