All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 73504] Segfault in _save_Normal3fv running FlightGear
Date: Fri, 28 Feb 2014 00:17:20 +0000	[thread overview]
Message-ID: <bug-73504-502-MHXMdr9QfS@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-73504-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 635 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=73504

--- Comment #9 from Fredrik Höglund <fredrik@kde.org> ---
(In reply to comment #8)
> I've been running your patches for two weeks now forward porting them to
> current git master.  FlightGear has been perfectly stable with them.
> 
> Unfortunatley I now get compilation errors and since I don't know the code
> base at all they are kind of hard to fix. See any chance you can commit them
> to master?

Yeah, I will rebase them and see about getting them into master.

Thanks for testing!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1507 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2014-02-28  0:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-11 17:26 [Bug 73504] New: Segfault in _save_Normal3fv running FlightGear bugzilla-daemon
2014-01-24 14:19 ` [Bug 73504] " bugzilla-daemon
2014-01-24 14:20 ` bugzilla-daemon
2014-01-24 14:21 ` bugzilla-daemon
2014-01-27 22:11 ` bugzilla-daemon
2014-02-04 22:18 ` bugzilla-daemon
2014-02-04 22:20 ` bugzilla-daemon
2014-02-13 21:56 ` bugzilla-daemon
2014-02-27 21:38 ` bugzilla-daemon
2014-02-28  0:17 ` bugzilla-daemon [this message]
2019-09-18 19:12 ` bugzilla-daemon

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=bug-73504-502-MHXMdr9QfS@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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. 
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.