From: Leo Famulari <leo@famulari.name>
To: Mathieu Lirzin <mthl@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add nlopt.
Date: Sat, 9 Apr 2016 12:21:09 -0400 [thread overview]
Message-ID: <20160409162109.GB27895@jasmine> (raw)
In-Reply-To: <87a8l3832k.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 788 bytes --]
On Sat, Apr 09, 2016 at 12:54:43PM +0200, Mathieu Lirzin wrote:
> Leo Famulari <leo@famulari.name> writes:
>
> > On Fri, Apr 08, 2016 at 12:18:15PM +0200, Mathieu Lirzin wrote:
> >> Roel Janssen <roel@gnu.org> writes:
> >>
> >> > Strangely enough, I couldn't apply it either. I don't know what
> >> > happened.. I regenerated the patch, and now I was able to apply it to
> >> > my source tree. Hopefully it works for you too now.
> >>
> >> This problem has already happened to me last year. I suspect it is/was a
> >> bug in Git.
> >
> > I've attached the diffoscope report (HTML) between the first two patches
> > in this thread.
>
> Do you mean “attached” like in email attachment? If so then I don't see
> the attachment...
Gah, I do that all the time! :p
Here it is...
[-- Attachment #2: report.html --]
[-- Type: text/html, Size: 26605 bytes --]
next prev parent reply other threads:[~2016-04-09 16:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 11:26 [PATCH] gnu: Add nlopt Roel Janssen
2016-04-07 15:44 ` Leo Famulari
2016-04-07 20:42 ` Alex Kost
2016-04-07 20:49 ` Roel Janssen
2016-04-08 10:18 ` Mathieu Lirzin
2016-04-09 5:56 ` Leo Famulari
2016-04-09 10:54 ` Mathieu Lirzin
2016-04-09 16:21 ` Leo Famulari [this message]
2016-04-07 20:48 ` Alex Kost
2016-04-07 21:20 ` Roel Janssen
2016-04-07 21:40 ` Ludovic Courtès
2016-04-07 22:52 ` Roel Janssen
2016-04-09 14:38 ` Ludovic Courtès
2016-05-03 11:02 ` Roel Janssen
2016-05-03 11:47 ` Ludovic Courtès
2016-05-03 12:34 ` Roel Janssen
2016-05-03 20:02 ` Ludovic Courtès
2016-05-03 20:17 ` Roel Janssen
2016-05-04 8:38 ` Alex Kost
2016-05-04 8:52 ` Roel Janssen
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=20160409162109.GB27895@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=mthl@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).