From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: archer@sourceware.org
Subject: Fedora 14 branches merge by 2010-07-27
Date: Wed, 07 Jul 2010 20:58:00 -0000 [thread overview]
Message-ID: <20100707205847.GA9664@host0.dyn.jankratochvil.net> (raw)
Hi,
http://fedoraproject.org/wiki/Schedule
->
2010-07-27 Feature Freeze -- Planning & Development Ends
FYI Fedora-13 had these Archer branches:
archer-tromey-delayed-symfile2
archer-tromey-python
archer-pmuldoon-next-over-throw2
archer-jankratochvil-fortran-module2
archer-jankratochvil-watchpoint2
archer-jankratochvil-vla
archer-keiths-expr-cumulative
archer-jankratochvil-ifunc
Proposal for Fedora-14:
These branches probably remain:
archer-tromey-delayed-symfile2
archer-tromey-python (only extracted parts)
archer-pmuldoon-next-over-throw2
archer-jankratochvil-watchpoint2
archer-jankratochvil-vla
archer-jankratochvil-ifunc
Please comment these branches:
archer-tromey-optional-psymtab
= Make psymtabs optional; implement DWARF indexing proposal
archer-tromey-threaded-dwarf
= A branch off optional-psymtab that reads indices in background threads.
archer-tromey-imported-unit
= Support for DW_TAG_imported_unit. Untested.
archer-pmuldoon-python-value-infcall
= Inferior function calls from a Python value.
archer-swagiaal-upstream
= A branch to park patches by swagiaal while they get reviewed upstream
archer-swagiaal-work
= A development branch for Sami Wagiaalla
I would appreciate if you do on Fedora-14 branches you own:
merge cd4c6c46d781fe20f1a73c9e07c0fbc05bfc8a0c
(the last common commit before the gdb-7.2 branch)
Thanks,
Jan
next reply other threads:[~2010-07-07 20:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 20:58 Jan Kratochvil [this message]
2010-07-08 1:51 ` Tom Tromey
2010-07-08 9:52 ` Phil Muldoon
2010-07-08 15:37 ` Keith Seitz
2010-07-08 15:43 ` Jan Kratochvil
2010-07-08 18:35 ` Tom Tromey
2010-07-09 16:48 ` Fedora 14 branches merge by 2010-07-27 [new list] Jan Kratochvil
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=20100707205847.GA9664@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=archer@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).