From: Jelle Licht <jlicht@fsfe.org> To: 31190-done@debbugs.gnu.org, 31219-done@debbugs.gnu.org Subject: bug#31190: Ansible doesn't build Date: Tue, 24 Apr 2018 13:50:15 +0200 [thread overview] Message-ID: <CAPsKtfL6DZkw+GEzHJWcogFha8gPSTcmsrQ+Qnb_DzbDm9DHDQ@mail.gmail.com> (raw) In-Reply-To: <87vacnc5pw.fsf@gnu.org> [-- Attachment #1: Type: text/plain, Size: 166 bytes --] I pushed my version of the patches that fix our ansible build as `09e3cf583437ce421215dd28d2b94f574458b311' and `acc6e6955f5d481cf984cafb0459d3489feda99e' to master. [-- Attachment #2: Type: text/html, Size: 217 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Jelle Licht <jlicht@fsfe.org> To: 31190-done@debbugs.gnu.org, 31219-done@debbugs.gnu.org Subject: bug#31219: bug#31190: Ansible doesn't build Date: Tue, 24 Apr 2018 13:50:15 +0200 [thread overview] Message-ID: <CAPsKtfL6DZkw+GEzHJWcogFha8gPSTcmsrQ+Qnb_DzbDm9DHDQ@mail.gmail.com> (raw) In-Reply-To: <87vacnc5pw.fsf@gnu.org> [-- Attachment #1: Type: text/plain, Size: 166 bytes --] I pushed my version of the patches that fix our ansible build as `09e3cf583437ce421215dd28d2b94f574458b311' and `acc6e6955f5d481cf984cafb0459d3489feda99e' to master. [-- Attachment #2: Type: text/html, Size: 217 bytes --]
next prev parent reply other threads:[~2018-04-24 11:51 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-17 9:40 bug#31190: Ansible doesn't build Clément Lassieur 2018-04-17 18:36 ` Jelle Licht 2018-04-17 20:56 ` Marius Bakke 2018-04-19 13:44 ` Jelle Licht 2018-04-19 16:04 ` Marius Bakke 2018-04-19 18:33 ` Clément Lassieur 2018-04-19 20:16 ` Roel Janssen 2018-04-24 11:50 ` Jelle Licht [this message] 2018-04-24 11:50 ` bug#31219: " Jelle Licht 2018-04-24 12:21 ` Clément Lassieur 2018-04-24 12:21 ` [bug#31219] " Clément Lassieur
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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAPsKtfL6DZkw+GEzHJWcogFha8gPSTcmsrQ+Qnb_DzbDm9DHDQ@mail.gmail.com \ --to=jlicht@fsfe.org \ --cc=31190-done@debbugs.gnu.org \ --cc=31219-done@debbugs.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: linkBe 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 external index https://git.savannah.gnu.org/cgit/guix.git This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.