public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "andre.poenitz at nokia dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/14502] New: Identify version Date: Tue, 21 Aug 2012 12:50:00 -0000 [thread overview] Message-ID: <bug-14502-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14502 Bug #: 14502 Summary: Identify version Product: gdb Version: unknown Status: NEW Severity: enhancement Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: andre.poenitz@nokia.com Classification: Unclassified When implementing a gdb frontend one needs to stay aware of which versions of gdb support a feature directly, for which there are workarounds, and which won't work at all. For that it would be nice if the documentation for specific options would contain a hint saying which is the first version of gdb supporting that option. A short "(since 7.2)" or similar would be sufficient. Right now it is seemingly needed to check out the source from git, find the implementation of the option, git blame the file, and make an educated guess based on the commit date. In the documentation of other projects that kind of information is immediately available. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-08-21 12:50 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-21 12:50 andre.poenitz at nokia dot com [this message] 2012-08-21 14:57 ` [Bug gdb/14502] " schwab@linux-m68k.org 2012-08-21 15:06 ` andre.poenitz at nokia 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-14502-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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).