From: Leo Famulari <leo@famulari.name>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 45523-done@debbugs.gnu.org
Subject: bug#45523: [PATCH 1/2] gnu: Add libyang
Date: Sat, 20 Feb 2021 18:04:31 -0500 [thread overview]
Message-ID: <YDGVfxDo41H57rdf@jasmine.lan> (raw)
In-Reply-To: <CAEwRq=ok6hQL=4ohzgtBp7qUG9bA4BbMbZ8zU5H0CK_7SRGbyA@mail.gmail.com>
On Sat, Feb 20, 2021 at 08:02:01PM +0100, Vincent Legoll wrote:
> Neither do I, you should have noticed I don't really know what
> I'm doing. Kind of a monkey packager I guess :-)
>
> I hope that's not too frightening.
No worries, everybody starts at the beginning!
> This looks related to Network Configuration Protocol
> (NETCONF), and I had to find a place for it, so I chose
> to put it near its user...
>
> WDYT ?
Alright, makes sense.
I pushed as 55fddf93079fa6e75bbe2d748c6abf8b5897d2c3 after updating
libyang to the latest (thanks to `guix lint` for letting me know about a
new release) and making sure that frrouting still builds.
Sorry these patches took so long to get in...
next prev parent reply other threads:[~2021-02-20 23:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 10:17 [bug#45523] [PATCH 0/2] Update for frrouting & add libyang Vincent Legoll
2020-12-29 10:20 ` [bug#45523] [PATCH 1/2] gnu: Add libyang Vincent Legoll
2020-12-29 10:20 ` [bug#45523] [PATCH 2/2] gnu: frrouting: Update to 7.5 Vincent Legoll
2020-12-31 0:11 ` [bug#45523] [PATCH 0/2] Update for frrouting & add libyang Leo Famulari
2021-01-05 10:57 ` [bug#45523] [PATCH 1/2] gnu: Add libyang Vincent Legoll
2021-01-05 10:57 ` [bug#45523] [PATCH 2/2] gnu: frrouting: Update to 7.5 Vincent Legoll
2021-02-20 18:49 ` [bug#45523] [PATCH 1/2] gnu: Add libyang Leo Famulari
2021-02-20 19:02 ` Vincent Legoll
2021-02-20 23:04 ` Leo Famulari [this message]
2021-01-05 11:00 ` [bug#45523] new patch set Vincent Legoll
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=YDGVfxDo41H57rdf@jasmine.lan \
--to=leo@famulari.name \
--cc=45523-done@debbugs.gnu.org \
--cc=vincent.legoll@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).