From: Brian Leung <bkleung89@gmail.com>
To: 36999@debbugs.gnu.org, Oleg Pykhalov <go.wigust@gmail.com>
Subject: [bug#36999] [PATCH] gnu: Add emacs-forge.
Date: Sun, 11 Aug 2019 19:39:09 +0200 [thread overview]
Message-ID: <CAAc=MExLy10n8RvUJ14bMU5qhTmgoJAsgoiNgy3x1J0iDi6diA@mail.gmail.com> (raw)
In-Reply-To: <20190810161809.4014-1-go.wigust@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 426 bytes --]
Hi Oleg,
I notice that emacs-forge, in its forge-pkg.el file, mentions newer
dependencies than what we currently have: ghub version 20190319, which
apparently contains a fix for a relevant bug; and Magit version 20190408.
I'm not sure how important the update to Magit is, and this newer version
of Magit also happens to depend on an additional package, libegit2. It
might be nice to update our version of ghub.
Best,
Brian
[-- Attachment #2: Type: text/html, Size: 526 bytes --]
next prev parent reply other threads:[~2019-08-11 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-10 16:18 [bug#36999] [PATCH] gnu: Add emacs-forge Oleg Pykhalov
2019-08-11 17:39 ` Brian Leung [this message]
2019-08-14 6:08 ` Brian Leung
2019-08-18 9:26 ` Oleg Pyhalov
2019-10-05 19:19 ` [bug#36999] [PATCH 0/4] More test and then merge to master Oleg Pykhalov
2019-10-05 19:19 ` [bug#36999] [PATCH 1/4] gnu: emacs-magit: Update to 2.90.1-1.c761d28 Oleg Pykhalov
2019-10-05 19:19 ` [bug#36999] [PATCH 2/4] gnu: emacs-ghub: Update to 3.2.0-1.cf0b13a Oleg Pykhalov
2019-10-05 19:19 ` [bug#36999] [PATCH 3/4] gnu: emacs-closql: Update to 1.0.0-1.70b98db Oleg Pykhalov
2019-10-05 19:19 ` [bug#36999] [PATCH 4/4] gnu: Add emacs-forge Oleg Pykhalov
2019-10-13 19:45 ` bug#36999: emacs-forge pushed to master Oleg Pykhalov
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAc=MExLy10n8RvUJ14bMU5qhTmgoJAsgoiNgy3x1J0iDi6diA@mail.gmail.com' \
--to=bkleung89@gmail.com \
--cc=36999@debbugs.gnu.org \
--cc=go.wigust@gmail.com \
/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/guix.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).