From: Bob Rossi <bob_rossi@cox.net>
To: gdb@sources.redhat.com
Subject: Adding file to gdb
Date: Sun, 09 Feb 2003 21:31:00 -0000 [thread overview]
Message-ID: <20030209213128.GB10166@white> (raw)
Is the gdb-patches@sources.redhat.com mailing list more appropriate for
this Email?
If I am going to submit a patch that adds a single file to gdb, do I
need to submit a patch of the Makefile changes also? Or will the
maintainer automatically fix the Makefile.am and configure code to do
this?
To be explicit, the file I added is src/gdb/mi/mi-cmd-file.c
The Makefile I edited was src/gdb/Makefile
The other files I modified are,
src/gdb/mi/ChangeLog -> Describing change
src/gdb/mi/gdbmi.texinfo -> Documenting change
src/gdb/mi/mi-cmds.c -> Added -file-list-exec-source-file
-> displays current line and absolute path
-> to file
src/gdb/mi/mi-cmds.h -> adds prototype of new mi function
Is this all I need to do? Or is there something else I should do
before I submit the patch?
Also, Should I do the context diff from src/ using 'cvs diff -c' ?
Thanks for your help,
Bobby
next reply other threads:[~2003-02-09 21:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 21:31 Bob Rossi [this message]
2003-02-09 22:06 Michael Elizabeth Chastain
2003-02-10 15:55 ` Bob Rossi
2003-02-10 16:19 Michael Elizabeth Chastain
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=20030209213128.GB10166@white \
--to=bob_rossi@cox.net \
--cc=gdb@sources.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