From: Christopher Baines <mail@cbaines.net>
To: Leo Famulari <leo@famulari.name>
Cc: 33308@debbugs.gnu.org
Subject: [bug#33308] [PATCH 0/2] Update mosh and capnproto.
Date: Mon, 26 Nov 2018 19:25:56 +0000 [thread overview]
Message-ID: <87r2f7abej.fsf@cbaines.net> (raw)
In-Reply-To: <20181107201919.GA29144@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 444 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Wed, Nov 07, 2018 at 07:45:30PM +0000, Christopher Baines wrote:
>> Update the mosh and capnproto packages. I want to update capnproto, and
>> I updated mosh along with it, as initially it failed to build with the
>> newer capnproto version.
>
> I got excited about a new release of mosh (the mobile shell). You mean
> mash, right? :)
Yep, sorry about that, I've fixed the title of the bug now.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 962 bytes --]
next prev parent reply other threads:[~2018-11-26 19:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 19:45 [bug#33308] [PATCH 0/2] Update mosh and capnproto Christopher Baines
2018-11-07 19:56 ` [bug#33308] [PATCH 1/2] gnu: mash: Update to 2.1 Christopher Baines
2018-11-07 19:56 ` [bug#33308] [PATCH 2/2] gnu: capnproto: Update to 0.7.0 Christopher Baines
2018-11-10 22:22 ` Ludovic Courtès
2018-11-26 19:27 ` Christopher Baines
2018-11-08 3:23 ` [bug#33308] [PATCH 1/2] gnu: mash: Update to 2.1 Eric Bavier
2018-11-26 19:35 ` Christopher Baines
2018-11-07 20:19 ` [bug#33308] [PATCH 0/2] Update mosh and capnproto Leo Famulari
2018-11-26 19:25 ` Christopher Baines [this message]
2018-11-26 19:04 ` [bug#33308] [PATCH v2 1/2] gnu: mash: Fix build with capnproto 0.7 Christopher Baines
2018-11-26 19:04 ` [bug#33308] [PATCH v2 2/2] gnu: capnproto: Update to 0.7.0 Christopher Baines
2018-12-05 20:34 ` bug#33308: " Christopher Baines
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=87r2f7abej.fsf@cbaines.net \
--to=mail@cbaines.net \
--cc=33308@debbugs.gnu.org \
--cc=leo@famulari.name \
/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).