From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: [BUG] Tab Expansion for C++
Date: Mon, 19 Feb 2007 12:28:00 -0000 [thread overview]
Message-ID: <20070219114749.GB6815@caradoc.them.org> (raw)
In-Reply-To: <200702190943.l1J9hQjj004616@mersenne.math.TU-Berlin.DE>
On Mon, Feb 19, 2007 at 10:43:26AM +0100, Thomas Richter wrote:
> All fine, but *which* document would need to be signed? Is there a template
> of sorts you can provide? The page above doesn't seem to provide details
> on this.
I sent Thomas the details off-list.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-02-19 11:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 16:28 Thomas Richter
2007-02-13 16:56 ` Daniel Jacobowitz
2007-02-13 17:08 ` Thomas Richter
2007-02-13 19:33 ` Daniel Jacobowitz
2007-02-14 12:08 ` Thomas Richter
2007-02-14 12:36 ` Daniel Jacobowitz
2007-02-19 11:48 ` Thomas Richter
2007-02-19 12:28 ` Daniel Jacobowitz [this message]
2007-02-19 13:03 ` Robert Dewar
2007-02-13 19:00 ` Andreas Schwab
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=20070219114749.GB6815@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@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