public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "scox at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/3894] assign<tab> doesn't append a space
Date: Fri, 16 Mar 2007 22:34:00 -0000 [thread overview]
Message-ID: <20070316223441.25993.qmail@sourceware.org> (raw)
In-Reply-To: <20070119230546.3894.cagney@redhat.com>
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|frysk-bugzilla at sourceware|scox at redhat dot com
|dot org |
Status|NEW |ASSIGNED
http://sourceware.org/bugzilla/show_bug.cgi?id=3894
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2007-03-16 22:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 23:05 [Bug general/3894] New: " cagney at redhat dot com
2007-03-16 22:34 ` scox at redhat dot com [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=20070316223441.25993.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=frysk-bugzilla@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).