On Friday, 10 January 2020 at 04:06:28 UTC, rikki cattermole
wrote:
You are.
It is an implementation detail, not policy.
To do it 100% generically dub repository will have to
understand each VCS system, check it out and then archive it
before shipping it off on request. Instead of just
On 10/01/2020 4:37 PM, suncarpet wrote:
If things were to change, I'd like for restrictions on where code is
hosted and the VCS to be loosened. I may be looking at this very
naively, however.
You are.
It is an implementation detail, not policy.
To do it 100% generically dub repository will
On Friday, 10 January 2020 at 03:14:29 UTC, James Blachly wrote:
On 1/9/20 10:03 PM, suncarpet wrote:
I can't say I like the idea of requiring users to use the
aforementioned or similar services and necessitating the use
of git over other VCS solutions.
How is it that dub works today?
It
On 1/9/20 10:03 PM, suncarpet wrote:
I can't say I like the idea of requiring users to use the aforementioned
or similar services and necessitating the use of git over other VCS
solutions.
How is it that dub works today?
On Friday, 10 January 2020 at 02:36:51 UTC, James Blachly wrote:
I am sorry to post on an older (but < 30 days!) thread that
I've just seen.
While it would be very reasonable for the Foundation to be
running this infra, Sebastiaan's proposal is quite right --
eliminate the need for a server
On 12/17/19 12:34 PM, H. S. Teoh wrote:
This looks like something the D Foundation ought to fund. Buy one of
the many VPS's out there to be used as the "official", Foundation-backed
dub server, preferably with a hosting provider that has multiple
redundant network connections and automatic
On Wednesday, 18 December 2019 at 10:18:03 UTC, Sebastiaan Koppe
wrote:
On Wednesday, 18 December 2019 at 09:29:50 UTC, John Colvin
wrote:
This is still down for me, regardless of using the IP or
address. I don't think it's just me either:
https://stats.uptimerobot.com/6mQX4Crw2L/783838659
On Wednesday, 18 December 2019 at 09:29:50 UTC, John Colvin wrote:
This is still down for me, regardless of using the IP or
address. I don't think it's just me either:
https://stats.uptimerobot.com/6mQX4Crw2L/783838659
https://downforeveryoneorjustme.com/code.dlang.org
Connection timeout
On Wednesday, 18 December 2019 at 11:03:04 UTC, Andrea Fontana
wrote:
On Wednesday, 18 December 2019 at 09:29:50 UTC, John Colvin
wrote:
This is still down for me, regardless of using the IP or
address. I don't think it's just me either:
https://stats.uptimerobot.com/6mQX4Crw2L/783838659
On Wednesday, 18 December 2019 at 09:29:50 UTC, John Colvin wrote:
This is still down for me, regardless of using the IP or
address. I don't think it's just me either:
https://stats.uptimerobot.com/6mQX4Crw2L/783838659
Anytime you see the metadata working you can add
On 12/18/19 12:29 PM, John Colvin wrote:
This is still down for me, regardless of using the IP or address. I
don't think it's just me either:
https://stats.uptimerobot.com/6mQX4Crw2L/783838659
The same with me. I can't visit code.dlang.org from home pc, but able to
do it from work one. (I
On Monday, 16 December 2019 at 11:04:38 UTC, Sönke Ludwig wrote:
As you may have already noticed, the main registry server,
code.dlang.org got unreachable yesterday. This was caused by an
old VPS of mine getting terminated. The registry had already
moved to a different server years ago, but,
On Tuesday, 17 December 2019 at 17:34:07 UTC, H. S. Teoh wrote:
On Tue, Dec 17, 2019 at 01:34:16AM +, bachmeier via
Digitalmars-d-announce wrote: [...]
Oh, I don't doubt that. My point was that it makes the D
language project look like a small-scale open source project
relying on
On Tue, Dec 17, 2019 at 01:34:16AM +, bachmeier via Digitalmars-d-announce
wrote:
[...]
> Oh, I don't doubt that. My point was that it makes the D language
> project look like a small-scale open source project relying on
> volunteers (in this case Sonke) being generous with time and
>
On Tuesday, 17 December 2019 at 01:34:16 UTC, bachmeier wrote:
Oh, I don't doubt that. My point was that it makes the D
language project look like a small-scale open source project
relying on volunteers (in this case Sonke) being generous with
time and resources. What manager is going to trust
On Tuesday, 17 December 2019 at 00:55:35 UTC, Pham wrote:
On Monday, 16 December 2019 at 22:43:58 UTC, bachmeier wrote:
On Monday, 16 December 2019 at 20:21:16 UTC, Temtaime wrote:
My ISP still serves old IP.
Thanks for such a blackout.
D is still not for production use, just a toy that may
On Tue, Dec 17, 2019 at 12:55:35AM +, Pham via Digitalmars-d-announce wrote:
> On Monday, 16 December 2019 at 22:43:58 UTC, bachmeier wrote:
> > On Monday, 16 December 2019 at 20:21:16 UTC, Temtaime wrote:
> > > My ISP still serves old IP.
> > > Thanks for such a blackout.
> > > D is still not
On Monday, 16 December 2019 at 22:43:58 UTC, bachmeier wrote:
On Monday, 16 December 2019 at 20:21:16 UTC, Temtaime wrote:
My ISP still serves old IP.
Thanks for such a blackout.
D is still not for production use, just a toy that may break
accidentally by a will of its creators.
I wish I
On Monday, 16 December 2019 at 20:21:16 UTC, Temtaime wrote:
My ISP still serves old IP.
Thanks for such a blackout.
D is still not for production use, just a toy that may break
accidentally by a will of its creators.
I wish I could disagree, but from the view of large enterprise
adoption,
My ISP still serves old IP.
Thanks for such a blackout.
D is still not for production use, just a toy that may break
accidentally by a will of its creators.
On Monday, 16 December 2019 at 11:04:38 UTC, Sönke Ludwig wrote:
As you may have already noticed, the main registry server,
code.dlang.org got unreachable yesterday. This was caused by an
old VPS of mine getting terminated. The registry had already
moved to a different server years ago, but,
Am 16.12.2019 um 12:23 schrieb WebFreak001:
On Monday, 16 December 2019 at 11:04:38 UTC, Sönke Ludwig wrote:
As you may have already noticed, the main registry server,
code.dlang.org got unreachable yesterday. This was caused by an old
VPS of mine getting terminated. The registry had already
On Monday, 16 December 2019 at 11:04:38 UTC, Sönke Ludwig wrote:
As you may have already noticed, the main registry server,
code.dlang.org got unreachable yesterday. This was caused by an
old VPS of mine getting terminated. The registry had already
moved to a different server years ago, but,
As you may have already noticed, the main registry server,
code.dlang.org got unreachable yesterday. This was caused by an old VPS
of mine getting terminated. The registry had already moved to a
different server years ago, but, without me realizing it, the DNS entry
still pointed to the old
24 matches
Mail list logo
