Dear friends,
as I'm working on making lib:ghc re-installable [1][2].
Ideally I'd prefer we only had to freeze rts + ghc-prim
and maybe base (which would implicate the integer library).
However, we apparently can't re-install Template Haskell
I'm told. Not just not upgrade it, but not even
Merging Haddock into GHC’s subtree would undoubtedly simplify the GHC workflow
for patches affecting Haddock. There are a couple other considerations though:
Haddock currently sees the bulk of its contributions and bug fixes on its
stable branches, not the ghc-head branch (which is the one GHC
"Boespflug, Mathieu" writes:
> If the status quo is poor, then why not merge the two? git-subtree won't
> fix the problem and will arguably be even harder to manage than submodules.
>
The status quo is indeed awkward at times. However, merging Haddock into
GHC would only serve to shuffle this
If the status quo is poor, then why not merge the two? git-subtree won't
fix the problem and will arguably be even harder to manage than submodules.
Best,
On Wed, 6 Mar 2019 at 15:59, Ben Gamari wrote:
> Sylvain Henry writes:
>
> > Why don't we just put Haddock into GHC's repository? It was
Can they be sent from a different email address than the main.
Gitlab+margebot are quite. Ahum, noisy.. and filtering based on message
content has a potential for false positives.
Kind regards,
Tamar
On Wed, Mar 6, 2019, 12:33 Matthew Pickering
wrote:
> I think gitlab can be configured so
I think that's a reliable replacement for the ghc-tickets mailing list if
it works well. I'll have to see once the cut-over happens!
On Wed, 6 Mar 2019 at 16:44, Ben Gamari wrote:
> Ara Adkins writes:
>
> > That would be perfect if so. I couldn't find a way to do it when I looked
> > earlier,
On Wed, Mar 6, 2019 at 11:39 AM Ben Gamari wrote:
> Shayne Fletcher via ghc-devs writes:
>
> > On Wed, Mar 6, 2019 at 11:09 AM Shayne Fletcher <
> > shayne.fletc...@digitalasset.com> wrote:
> >
> >>
> >>
> >>> On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari wrote:
> >>>
>
> Hello everyone,
Ara Adkins writes:
> That would be perfect if so. I couldn't find a way to do it when I looked
> earlier, but I may well have missed something!
>
If you navigate to the GHC project page [1] while logged in you should
find a little bell [2] button to the right of the "GHC" heading. If you
click
Shayne Fletcher via ghc-devs writes:
> On Wed, Mar 6, 2019 at 11:09 AM Shayne Fletcher <
> shayne.fletc...@digitalasset.com> wrote:
>
>>
>>
>>> On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari wrote:
>>>
Hello everyone,
The GHC team is very happy to announce the availability of GHC
You probably want to use the gitlab remote rather than the git.haskell.org
one.
Matt
On Wed, Mar 6, 2019 at 4:16 PM Shayne Fletcher via ghc-devs <
ghc-devs@haskell.org> wrote:
>
> On Wed, Mar 6, 2019 at 11:09 AM Shayne Fletcher <
> shayne.fletc...@digitalasset.com> wrote:
>
>>
>>
>>> On Tue,
On Wed, Mar 6, 2019 at 11:09 AM Shayne Fletcher <
shayne.fletc...@digitalasset.com> wrote:
>
>
>> On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari wrote:
>>
>>>
>>> Hello everyone,
>>>
>>> The GHC team is very happy to announce the availability of GHC 8.6.4, a
>>> bugfix release in the GHC 8.6 series.
On Wed, Mar 6, 2019 at 10:59 AM Shayne Fletcher <
shayne.fletc...@digitalasset.com> wrote:
> Sorry if you get two of these messages (having some email client problems
> :) )!
>
> Hi Ben,
>
> On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari wrote:
>
>>
>> Hello everyone,
>>
>> The GHC team is very happy
Sorry if you get two of these messages (having some email client problems
:) )!
Hi Ben,
On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari wrote:
>
> Hello everyone,
>
> The GHC team is very happy to announce the availability of GHC 8.6.4, a
> bugfix release in the GHC 8.6 series.
>
There doesn't seem
Hi Ben,
On Tue, Mar 5, 2019 at 3:53 PM Ben Gamari wrote:
>
> Hello everyone,
>
> The GHC team is very happy to announce the availability of GHC 8.6.4, a
> bugfix release in the GHC 8.6 series.
>
There doesn't seem to be a ghc-8.6.4-release tag of
http://git.haskell.org/ghc.git? Can you advise
Sylvain Henry writes:
> Why don't we just put Haddock into GHC's repository? It was proposed in
> a previous discussion in February [1] and it would avoid the bad
> experience of having it as a submodule while keeping it in sync.
>
I'm reluctant to keep it in the GHC tree; it really is a
Why don't we just put Haddock into GHC's repository? It was proposed in
a previous discussion in February [1] and it would avoid the bad
experience of having it as a submodule while keeping it in sync.
With the following commands we can keep the whole commit history:
In Haddock repo:
> mkdir
> I've opened #16398 to track this. We'll try to fix this before 8.8.1.
Thanks for doing that!
Regards,
Takenobu
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
For context: there is a total of 22 pages that use the redirect feature.
So it may actually be feasible to just do this manually.
On Wed, Mar 06, 2019 at 01:05:28PM +0100, Tobias Dammers wrote:
> On Wed, Mar 06, 2019 at 06:09:35AM -0500, Ben Gamari wrote:
> > The lacking redirect support is
That would be perfect if so. I couldn't find a way to do it when I looked
earlier, but I may well have missed something!
On Wed, 6 Mar 2019 at 12:33, Matthew Pickering
wrote:
> I think gitlab can be configured so notifications are sent for new issues
> and comments on issues which should
I think gitlab can be configured so notifications are sent for new issues
and comments on issues which should achieve the same thing as the mailing
list did?
On Wed, Mar 6, 2019 at 12:00 PM Sylvain Henry wrote:
> I use it to track tickets and I would also like to see it continued.
>
> Sylvain
Takenobu Tani writes:
> Hi,
>
> I always appreciate your hard work.
>
> Perhaps you may know, but the following html documents are not included in
> the windows tarball [1]:
>
> * doc/html/index.html
> * doc/html/users_guide/index.html
> * doc/html/libraries/index.html
>
Thanks Takenobu! I
Hi,
I always appreciate your hard work.
Perhaps you may know, but the following html documents are not included in
the windows tarball [1]:
* doc/html/index.html
* doc/html/users_guide/index.html
* doc/html/libraries/index.html
These files were included in ghc-8.6.3 tarball [2].
These
Ryan Scott writes:
> I do think something is afoot here. The current Haddock submodule commit is
> at 07f2ca [1], but the ghc-head branch of Haddock is still at commit 8459c6
> [2]. It would be good if someone could update the ghc-head branch
> accordingly.
>
Indeed. Done.
It would be nice if
On Wed, Mar 06, 2019 at 06:09:35AM -0500, Ben Gamari wrote:
> The lacking redirect support is unfortunate. In my opinion this is something
> we will need to handle going forward as well; a one time solution like adding
> nginx redirects doesn't seem like the right approach to me.
>
> I would
I use it to track tickets and I would also like to see it continued.
Sylvain
On 06/03/2019 12:33, Ara Adkins wrote:
Personally I would like to see it continued, but it may not be worth the work
if I’m in a minority here.
A potential stopgap would be to ‘watch’ the GHC project on our gitlab
Personally I would like to see it continued, but it may not be worth the work
if I’m in a minority here.
A potential stopgap would be to ‘watch’ the GHC project on our gitlab instance,
but I can’t see any way to decide to get emails for notifications rather than
having to check in at GitLab
On March 6, 2019 6:11:49 AM EST, Ara Adkins wrote:
>Super excited for this! Thank you to everyone whose put in so much hard
>work to get it done!
>
>One question: what is happening with the trac tickets mailing list? I
>imagine it’ll be going away, but for those of us that use it to keep
>track
I do think something is afoot here. The current Haddock submodule commit is
at 07f2ca [1], but the ghc-head branch of Haddock is still at commit 8459c6
[2]. It would be good if someone could update the ghc-head branch
accordingly.
Ryan S.
-
[1]
Super excited for this! Thank you to everyone whose put in so much hard work to
get it done!
One question: what is happening with the trac tickets mailing list? I imagine
it’ll be going away, but for those of us that use it to keep track of things is
there a recommended alternative?
Best,
The lacking redirect support is unfortunate. In my opinion this is something we
will need to handle going forward as well; a one time solution like adding
nginx redirects doesn't seem like the right approach to me.
I would rather advocate either option 3 or one of the following options:
5.
On March 6, 2019 1:32:44 AM EST, "Ömer Sinan Ağacan"
wrote:
>This look great, thanks to everyone involved!
>
>Some feedback:
>
>- When I click to the "Wiki" link on the left it opens "Home" page and
>I don't
>know how to go to the index from there. I think we may want index to be
>the
> home
On March 6, 2019 4:23:37 AM EST, Simon Peyton Jones
wrote:
>| * Tickets will have notes added when they are mentioned by a commit
>| message. As we discussed earlier, messages won't include the
>commit
>| message text but rather only a reference to the referring commit
>SHA.
>|
On March 6, 2019 2:06:25 AM EST, Bryan Richter wrote:
>Ben wrote:
>> Unfortunately a mention of a ticket from a commit does not produce
>a notification email. This is in my opinion a rather serious issue that
>we will need to work around since it makes closing tickets after merge
>far
>more
Yes I'm pointing to gitlab.
[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = https://gitlab.haskell.org/ghc/ghc.git
pushurl = g...@gitlab.haskell.org:ghc/ghc
I have done
git submodule sync
git submodule init
git submodule update
I just pulled master and `git submodule update` worked. Have you done `git
submodule sync` after updating your remotes to point to Gitlab? I'd try doing
that and then `git submodule update --init` again afterwards.
Ömer
Simon Peyton Jones via ghc-devs , 6 Mar 2019
Çar, 12:57 tarihinde şunu
Devs
In a clean, up-to-date master I try to say
Bash$ git submodule update
fatal: reference is not a tree: 07f2ca98fd4249dc6ebad053bd6aef90c814efe0
Unable to checkout '07f2ca98fd4249dc6ebad053bd6aef90c814efe0' in submodule path
'utils/haddock'
What should I do?
Thanks
Simon
| * Tickets will have notes added when they are mentioned by a commit
| message. As we discussed earlier, messages won't include the commit
| message text but rather only a reference to the referring commit SHA.
| For instance, this looks like [1].
I thought we'd decided, for now
37 matches
Mail list logo
