This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: How do I submit a patch that adds files?
- To: Michael Elizabeth Chastain <chastain at cygnus dot com>
- Subject: Re: How do I submit a patch that adds files?
- From: jtc at redback dot com (J.T. Conklin)
- Date: 29 Jan 2001 15:22:24 -0800
- Cc: gdb-patches at sourceware dot cygnus dot com
- References: <200101292305.PAA19067@bosch.cygnus.com>
- Reply-To: jtc at redback dot com
>>>>> "Michael" == Michael Elizabeth Chastain <chastain@cygnus.com> writes:
Michael> OK, I've got write-after-approval access and I want to add a new
Michael> test script:
Michael>
Michael> gdb/testsuite/gdb.base/structs3.exp
Michael> gdb/testsuite/gdb.base/structs3.c
Michael>
Michael> When I do "cvs diff", it gives me some useless ? messages:
Michael>
Michael> ? gdb/testsuite/gdb.base/structs3.exp
Michael> ? gdb/testsuite/gdb.base/structs3.c
Michael>
Michael> As far as I know, my next CVS move would be "cvs add structs3.exp",
Michael> but I don't have authority to do that on the repository.
Michael>
Michael> What is the procedure for me to submit a patch that adds new files?
To the best of my knowledge, CVS does not change the repository with
"cvs add", only local meta-data in your sandbox is updated. If this
is still the case, you could "cvs add", and then "cvs diff -N".
--jtc
--
J.T. Conklin
RedBack Networks