public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug admin/13746] auto-annotate bugzilla from git commits
Date: Tue, 15 Oct 2013 15:01:00 -0000	[thread overview]
Message-ID: <bug-13746-131-mGUXfWIyGX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-13746-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=13746

--- Comment #9 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Tom Tromey from comment #8)
> (In reply to Carlos O'Donell from comment #7)
> 
> > 
> > Do you know this because you just enabled it for gdb and it works?
> 
> I wrote it for the gdb/binutils git conversion and spent last week
> trying it out.
> It's possible that it still has bugs of course, but I think it is
> reasonably well-debugged.
> 
> > If it works for gdb I'd love to just turn it on for glibc.
> > 
> > Do I just ask overseers for help?
> 
> I can do it if you like.

Please do. Between Roland, H.J. Lu, Joseph, and myself that's enough consensus
to enable this for glibc. We're happy to work out any kinks.

Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-10-15 15:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 18:01 [Bug admin/13746] New: " roland at gnu dot org
2012-06-21 17:16 ` [Bug admin/13746] " hjl.tools at gmail dot com
2013-03-20 12:25 ` jsm28 at gcc dot gnu.org
2013-03-20 14:51 ` carlos at redhat dot com
2013-03-21 22:58 ` carlos at redhat dot com
2013-08-12  9:04 ` tromey at redhat dot com
2013-10-15 13:38 ` tromey at redhat dot com
2013-10-15 13:50 ` carlos at redhat dot com
2013-10-15 14:00 ` tromey at redhat dot com
2013-10-15 15:01 ` carlos at redhat dot com [this message]
2013-10-15 15:27 ` joseph at codesourcery dot com
2013-10-15 15:35 ` tromey at redhat dot com
2013-10-18 15:56 ` tromey at redhat dot com
2013-10-18 16:27 ` carlos at redhat dot com
2013-10-20  8:45 ` schwab@linux-m68k.org
2013-10-24  8:21 ` schwab@linux-m68k.org
2013-10-24 15:33 ` joseph at codesourcery dot com
2013-10-24 16:46 ` carlos at redhat dot com
2013-10-24 19:30 ` tromey at redhat dot com
2013-10-25 15:15 ` joseph at codesourcery dot com
2013-10-25 21:05 ` tromey at redhat dot com
2014-02-16 18:25 ` jackie.rosen at hushmail dot com
2014-05-28 19:43 ` schwab at sourceware dot org
2014-06-26 15:15 ` fweimer at redhat dot com

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-13746-131-mGUXfWIyGX@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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 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).