Re: Can't push to haddock

cember 2017 09:30 > To: Herbert Valerio Riedel <hvrie...@gmail.com> > Cc: Simon Peyton Jones <simo...@microsoft.com>; ghc-devs@haskell.org Devs > <ghc-devs@haskell.org> > Subject: Re: Can't push to haddock > > 2017-12-19 9:50 GMT+01:00 Herbert Valerio Riedel <

Re: Can't push to haddock

Thank you for that word of reason. (In addition to your very well stated point, the whole point of Git is that it is a *distributed* RCS. I don’t think, anything less than a full scale planetary nuclear war could really wipe out the GHC source code at this point.) Manuel > 20.12.2017 05:02

Re: Can't push to haddock

> You're also assuming github doesn't suddenly pull a SourceForge (or a > Gitorious for that matter). Business cares not what it steamrolls in the > name of profit. > > I fail to understand why, with multiple examples of the folly of this > belief out there, people are still willing to bet on

Re: Can't push to haddock

On Tue, Dec 19, 2017 at 4:30 AM, Sven Panne wrote: > I think this is a question of perspective: Having the master repository on > GitHub doesn't mean you are in immediate danger or lose your "family > jewels". IMHO it's quite the contrary: I'm e.g. sure that in case that >

Re: Can't push to haddock

2017-12-19 12:47 GMT+01:00 Phyx : > Cool, then let's turn to media reports then such as > https://techcrunch.com/2017/07/31/github-goes-down-and-takes-developer- > productivity-with-it/ do you have one for git.haskell.org going down? Of course this question is a classic

Re: Can't push to haddock

2017-12-19 11:07 GMT+01:00 Phyx : > These are just a few of the times github has been down in 2017 > http://currentlydown.com/github.com compared to haskell.org http:// > currentlydown.com/haskell.org [...] > I can't see any data for haskell.org on that page, apart from the

RE: Can't push to haddock

was not the case five years ago). Simon From: Sven Panne [mailto:svenpa...@gmail.com] Sent: 19 December 2017 09:30 To: Herbert Valerio Riedel <hvrie...@gmail.com> Cc: Simon Peyton Jones <simo...@microsoft.com>; ghc-devs@haskell.org Devs <ghc-devs@haskell.org> Subject: Re: Can't pus

Re: Can't push to haddock

2017-12-19 9:50 GMT+01:00 Herbert Valerio Riedel : > We'd need mirroring anyway, as we want to keep control over our > infrastructure and not have to trust a 3rd party infrastructure to > safely handle our family jewels: GHC's source tree. > I think this is a question of

Re: Can't push to haddock

Hi, On 2017-12-19 at 08:31:06 +0100, Sven Panne wrote: > This is a tradeoff: Doing it that way, you catch incorrect commits a > little bit later, but it makes the overall arcane repository magic > quite a bit simpler, probably removing the need for mirroring. We'd need mirroring anyway, as we

Re: Can't push to haddock

2017-12-18 17:01 GMT+01:00 Simon Peyton Jones via ghc-devs < ghc-devs@haskell.org>: > | It's for technical reasons, and the strongest one being: GitHub doesn't > | allow us to establish strong invariants regarding submodule gitlink > | referential integrity for submodules (which I implemented

RE: Can't push to haddock

...@gmail.com] | Sent: 18 December 2017 11:13 | To: Simon Peyton Jones <simo...@microsoft.com> | Subject: Re: Can't push to haddock | | On Mon, Dec 18, 2017 at 10:01 AM, Simon Peyton Jones via ghc-devs wrote: | > But why don’t we just pull from github rather than mirroring on | > git

RE: Can't push to haddock

re there's a rationale but I don't get it yet. Simon | -Original Message- | From: Herbert Valerio Riedel [mailto:hvrie...@gmail.com] | Sent: 07 December 2017 17:57 | To: Simon Peyton Jones <simo...@microsoft.com> | Subject: Re: Can't push to haddock | | Hi Simon, | | Yes, t

RE: Can't push to haddock

r 2017 17:32 To: ghc-devs@haskell.org Subject: Can't push to haddock I'm trying to push a patch that needs a supporting change to haddock. I've pushed the haddock change to the ghc-head branch of ssh://g...@github.com/haskell/haddock.git, which is (according to 'packages') the relevant haddock u

Can't push to haddock

I'm trying to push a patch that needs a supporting change to haddock. I've pushed the haddock change to the ghc-head branch of ssh://g...@github.com/haskell/haddock.git, which is (according to 'packages') the relevant haddock upstream repo. But when I try to push the GHC patch, I get this

RE: Can't push to haddock repo

Simon Peyton Jones writes: > Well in utils/haddock/.git/config I see > [remote "origin"] > url = git://git.haskell.org/haddock.git > pushurl = ssh://g...@git.haskell.org/haddock.git > Note the difference in hostnames,

Can't push to haddock repo

I can't update the haddock repository! (I want to add a new branch for my in-flight work.) Can anyone help? Thanks Simon git push --set-upstream origin wip/spj-wildcard-refactor remote: W refs/heads/wip/spj-wildcard-refactor haddock simonpj DENIED by refs/.* remote: error: hook declined to

Re: Can't push to haddock repo

In the GHC tree: $ grep haddock packages utils/haddock- - ssh://g...@github.com/haskell/haddock.git says that the upstream repo for Haddock is ssh://... (there are some comments in the 'packages' file that explain what the last column

RE: Can't push to haddock repo

ilto:hvrie...@gmail.com] | Sent: 26 October 2015 13:04 | To: Simon Peyton Jones | Cc: ghc-devs@haskell.org | Subject: Re: Can't push to haddock repo | | | In the GHC tree: | | $ grep haddock packages | utils/haddock- - | ssh://g...@github.com/haskell/haddock.git

RE: Can't push to haddock repo

ah yes, my bad. Thanks | -Original Message- | From: Ben Gamari [mailto:b...@well-typed.com] | Sent: 26 October 2015 13:55 | To: Simon Peyton Jones; Herbert Valerio Riedel | Cc: ghc-devs@haskell.org | Subject: RE: Can't push to haddock repo | | Simon Peyton Jones <s