From: Roman Kennke <roman@kennke.org>
To: Olivier Jolly <olivier.jolly@pcedev.com>
Cc: mauve-patches@sourceware.org
Subject: Re: Proposed test on serialization back references
Date: Thu, 02 Feb 2006 22:14:00 -0000 [thread overview]
Message-ID: <1138918439.9591.80.camel@localhost.localdomain> (raw)
In-Reply-To: <43E28024.8090704@pcedev.com>
[-- Attachment #1: Type: text/plain, Size: 495 bytes --]
Hi Oliview,
Am Donnerstag, den 02.02.2006, 22:56 +0100 schrieb Olivier Jolly:
> Hi,
> for my first patch that I could commit myself, I prefer to ensure I'm
> not doing something wrong and to begin with a trivial test (I got a more
> interesting one with an actual classpath bug and the classpath fix that
> I will add at the same time when I'll also get the write access on
> classpath).
> Thanks for the feedback.
This looks good, please go ahead and commit this.
/Roman
[-- Attachment #2: Dies ist ein digital signierter Nachrichtenteil --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2006-02-02 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 21:56 Olivier Jolly
2006-02-02 22:14 ` Roman Kennke [this message]
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=1138918439.9591.80.camel@localhost.localdomain \
--to=roman@kennke.org \
--cc=mauve-patches@sourceware.org \
--cc=olivier.jolly@pcedev.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).