From: ng0 <ng0@n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29306@debbugs.gnu.org
Subject: [bug#29306] network-manager-vpnc
Date: Mon, 17 Jun 2019 14:05:50 +0000 [thread overview]
Message-ID: <20190617140550.5v3pguhvxqmwug7c@uptimegirl> (raw)
In-Reply-To: <877e9kxri6.fsf@gnu.org>
Hi Ludovic and Jelle,
Ludovic Courts transcribed 654 bytes:
> Heya,
>
> Jelle Licht <jlicht@fsfe.org> skribis:
>
> > ludo@gnu.org (Ludovic Courtès) writes:
> >
> >> Heya ng0,
> >>
> >> ng0 <ng0@infotropique.org> skribis:
> >>
> >>> From 0cf7c178f8453ffa0984d1f6e18efb61cf55d0d2 Mon Sep 17 00:00:00 2001
> >>> From: ng0 <ng0@infotropique.org>
> >>> Date: Wed, 15 Nov 2017 10:40:46 +0000
> >>> Subject: [PATCH] gnu: Add network-manager-vpnc.
> >>>
> >>> * gnu/packages/gnome.scm (network-manager-vpnc): New variable.
> >
> > Is this still being worked on/relevant? If so, I would like to verify
> > that it does what we want it to do, and get it merged :-).
Feel free to take on this. I have started publishing my old patches,
so there could be some progress in there.
Consider all my open patches here (I have no idea how many) up for
taking (leaving me as co/author), since I'm mainly doing NetBSD and
GNUnet these days.
The last known state of this patch is here:
https://c.n0.is/infotropique/p2/infotropiqueOScore/ports-wip/file/tip/ports/net/network-manager-vpnc/network-manager-vpnc.scm
Cheers,
ng0
> Please give it a spin! It’s sad to see patches bitrot.
>
> Cheers,
> Ludo’.
next prev parent reply other threads:[~2019-06-17 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 10:45 [bug#29306] network-manager-vpnc ng0
2017-11-16 9:25 ` Ludovic Courtès
2019-06-17 10:26 ` Jelle Licht
2019-06-17 13:37 ` Ludovic Courtès
2019-06-17 14:05 ` ng0 [this message]
2020-03-15 16:22 ` bug#29306: network-manager-vpnc Maxim Cournoyer
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=20190617140550.5v3pguhvxqmwug7c@uptimegirl \
--to=ng0@n0.is \
--cc=29306@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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).