From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, juri@linkov.net
Subject: Re: Adding problems to an existing bug report, was: Re: bug#23179: 25.0.92; Restore `M-,' to continue etags search
Date: Wed, 8 May 2019 14:07:21 +0300 [thread overview]
Message-ID: <cab4bf31-1eed-cdc0-8c8a-d40d8732695f@yandex.ru> (raw)
In-Reply-To: <83bm0nsdvf.fsf@gnu.org>
On 30.04.2019 18:37, Eli Zaretskii wrote:
> Does anyone know how to use that to browse some GitLab issue, e.g. the
> one posted by Toon? I tried to do that, but got only error messages.
> I suspect that I didn't understand how to use the package.
Unfortunately, no. It looks pretty broken. I got to the list of issues
on our EMBA Gitlab installation, but the available features are pretty
bare (reading the comments doesn't work after all). And the same
scenario didn't work for gitlab.com because one of the steps is "browse
all projects". This seems to lead to a timeout. All in all, I wouldn't
recommend this project in its current state.
People have previously recommended Forge, and I'm looking into it, but
it's tied to Magit, and the workflow is such that you first check out
the repository locally, they you set up its "forge" from the Magit UI,
and then you can interact with it.
It's supposedly quite functional, but visiting a random issue on Gitlab
is not that easy to do.
prev parent reply other threads:[~2019-05-08 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABr8ebb_=-1X-rAcaYEKFOY72K59hkqD_YJJgN7-RfO9j4LAhw@mail.gmail.com>
[not found] ` <48066d7c-e4d3-acf5-fdcf-1aa9a108cb90@yandex.ru>
[not found] ` <1554100819364-0.post@n8.nabble.com>
[not found] ` <CC2756D1-3BDD-43FF-A90E-29BA64A2E9D3@gnu.org>
[not found] ` <1554216459522-0.post@n8.nabble.com>
[not found] ` <83mul8fn8d.fsf@gnu.org>
[not found] ` <7d450c54-d4f5-b871-91e5-b00019ff323a@yandex.ru>
[not found] ` <87pnpy6cau.fsf@mail.linkov.net>
[not found] ` <32a0a910-772e-add8-0042-8a7faaea0eb7@yandex.ru>
[not found] ` <87ef5r16tv.fsf@mail.linkov.net>
[not found] ` <c5e88431-9726-c56f-b729-e93a6aafc395@yandex.ru>
[not found] ` <875zqx4yw4.fsf@mail.linkov.net>
2019-04-29 21:35 ` Adding problems to an existing bug report, was: Re: bug#23179: 25.0.92; Restore `M-,' to continue etags search Dmitry Gutov
2019-04-30 15:37 ` Eli Zaretskii
2019-05-08 11:07 ` Dmitry Gutov [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cab4bf31-1eed-cdc0-8c8a-d40d8732695f@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).