From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bzip2: change upstream site
Date: Mon, 13 Aug 2018 17:50:21 +0200 [thread overview]
Message-ID: <20180813155021.GC7915@scaer> (raw)
In-Reply-To: <20180813040557.th5v3ftbpixgppsg@sapphire.tkos.co.il>
Baruch, All,
On 2018-08-13 07:05 +0300, Baruch Siach spake thusly:
> On Sun, Aug 12, 2018 at 11:33:45AM +0200, Yann E. MORIN wrote:
> > On 2018-08-10 07:24 +0300, Baruch Siach spake thusly:
> > > The bzip.org website is down. Use the Buildroot backup download site.
> > > Change the website link to a gitlab repo that mirrors the content of the
> > > tarball.
> > >
> > > https://lwn.net/Articles/762264/
[--SNIP--]
> > > - http://www.bzip.org
> > > + https://gitlab.com/bzip/bzip2
> >
> > Not sure this is the best upstream location. [...]
> In my opinion, the best option at this point is to drop this link entirely. We
> can always put it back when "real" upstream reappears.
>
> What do you think?
100% agreed, thanks! :-)
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. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2018-08-13 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 4:24 [Buildroot] [PATCH] bzip2: change upstream site Baruch Siach
2018-08-12 9:33 ` Yann E. MORIN
2018-08-13 4:05 ` Baruch Siach
2018-08-13 15:50 ` Yann E. MORIN [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=20180813155021.GC7915@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.