Richard Eisenberg writes:
> Hi all,
>
> I've just reviewed !364, and it was a painful experience. Perhaps
> documenting why will help spur more UI innovations.
>
Indeed. Thanks for making sure these issues don't fall by the wayside.
> I believe this is easy to fix: make the Discussions tab
>
Richard Eisenberg writes:
> Very helpfully, that document now has GitLab issue numbers. I just
> pinged the one about the discussions tab.
>
> One issue in that document that doesn't have a GitLab Issue number is
> "Issue 5: Prioritising numbers". Ben (or others who have interfaced
> with GL
Very helpfully, that document now has GitLab issue numbers. I just pinged the
one about the discussions tab.
One issue in that document that doesn't have a GitLab Issue number is "Issue 5:
Prioritising numbers". Ben (or others who have interfaced with GL central): has
this been reported
I agree. It's frustrating.
I spent quite a bit of effort distilling ideas to help make GitLab better here:
https://docs.google.com/document/d/1sdGlDJSTiBZSH6kBU5pyn1HASE9XFqQhzILcYcH1QJQ/edit?usp=sharing
We shared those ideas with them, and I believe they promised to think about
them. I
Hi all,
I've just reviewed !364, and it was a painful experience. Perhaps documenting
why will help spur more UI innovations.
- My review was in response to several of the author's in-line comments, which
themselves were in response to previous in-line comments. This has to be a
common
Hi all,
I plan to do some work on the heap profiler during Zurihac this year.
I've written down quite a long list of possible projects if anyone
else wants to work on this with me. They are split into two
categories.
1. Improving my replacement for hp2ps/hp2pretty which parses and
renders
Hi Vlatko,
Unless this is a side effect of calling getrusage() (perhaps it causes the OS to
update stats) I don't see how this is possible.
Your reproducer seems to require postgres so I'm unable to run it. If you can
provide a version that doesn't need postgres I can take a look.
Ömer
Vlatko
