From: Glenn Morris <rgm@gnu.org>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: 14436@debbugs.gnu.org
Subject: bug#14436: 24.3.50; cscope + compilation-mode
Date: Wed, 22 May 2013 16:12:35 -0400 [thread overview]
Message-ID: <9m1u8yrcy4.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87ppwj7cnc.fsf@gmail.com> (Jambunathan K.'s message of "Wed, 22 May 2013 11:57:03 +0530")
Please don't send us patches.
We can't use them becase you don't have an assignment (and are way
past any tiny change limit).
The most helpful thing you can do is describe issues in full detail
without code so that someone else can fix them.
(This is a simple statement of facts, I'm not interested in starting a
discussion.)
next prev parent reply other threads:[~2013-05-22 20:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 6:27 bug#14436: 24.3.50; cscope + compilation-mode Jambunathan K
2013-05-22 20:12 ` Glenn Morris [this message]
2013-05-25 16:48 ` Jambunathan K
2013-11-15 4:48 ` Jambunathan K
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9m1u8yrcy4.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=14436@debbugs.gnu.org \
--cc=kjambunathan@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).