From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: archer@sourceware.org
Subject: Re: Brief stats for Fedora *.patch merge
Date: Mon, 01 Nov 2010 21:14:00 -0000 [thread overview]
Message-ID: <20101101211441.GA21861@host0.dyn.jankratochvil.net> (raw)
In-Reply-To: <m3lj5c92nd.fsf@fleche.redhat.com>
On Mon, 01 Nov 2010 22:04:22 +0100, Tom Tromey wrote:
> Also, I think we should pick a day or two in November to have a Fedora
> patch submit-a-thon. How about, say, Nov 18 and 19?
OK, I will try to rebase it till that time, stats will change a bit.
Jan
next prev parent reply other threads:[~2010-11-01 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 17:36 Jan Kratochvil
2010-11-01 21:00 ` Tom Tromey
2010-11-01 21:14 ` Jan Kratochvil [this message]
2010-11-18 4:42 ` Fedora 15 patchset rebased to FSF GDB HEAD [Re: Brief stats for Fedora *.patch merge] Jan Kratochvil
2010-11-18 15:58 ` Phil Muldoon
2010-11-19 21:05 ` Tom Tromey
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=20101101211441.GA21861@host0.dyn.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=archer@sourceware.org \
--cc=tromey@redhat.com \
/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).