From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: archer@sourceware.org
Subject: Re: Fedora 13: Please update your branch with "master"
Date: Fri, 08 Jan 2010 21:06:00 -0000 [thread overview]
Message-ID: <m31vi0xq54.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20100106231026.GA22942@host0.dyn.jankratochvil.net> (Jan Kratochvil's message of "Thu, 7 Jan 2010 00:10:26 +0100")
Jan> archer-pmuldoon-next-over-throw
Jan> archer-tromey-delayed-symfile
Jan> archer-tromey-python
I merged master into each of these.
I needed a slightly newer master for next-over-throw due to a
since-fixed bug on the trunk. So, delayed-symfile lags a little... if
that matters, let me know and I can do another merge to it.
I ran the test suite for regressions. There was one that turned out to
be an upstream regression. I fixed this in CVS but didn't pull the fix
in, because it is a trivial test suite bug. There are also a few tests
which failed unreproducibly.
Finally, I made a few minor changes (to fix regressions) in the code
while doing the merge. In retrospect I think this was a mistake, I
probably should have done separate commits.
Tom
next prev parent reply other threads:[~2010-01-08 21:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 23:10 Jan Kratochvil
2010-01-07 20:10 ` Tom Tromey
2010-01-08 21:06 ` Tom Tromey [this message]
2010-01-08 21:21 ` 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=m31vi0xq54.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=archer@sourceware.org \
--cc=jan.kratochvil@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).