This is the mail archive of the
sourcenav@sources.redhat.com
mailing list for the Source Navigator.
Re: bug fix for goto problem
- To: "Khamis Abuelkomboz (UUNET)" <khamis at knuut dot de>
- Subject: Re: bug fix for goto problem
- From: Tom Tromey <tromey at redhat dot com>
- Date: 09 Apr 2001 13:17:33 -0600
- Cc: sourcenav at sources dot redhat dot com
- References: <3AD1DE49.7030500@knuut.de>
- Reply-To: tromey at redhat dot com
>>>>> "Khamis" == Khamis Abuelkomboz (UUNET) <khamis@knuut.de> writes:
Khamis> since I want to work with SN5.0, because it's alot faster,
Khamis> I was forced to fix another nasty bug....
Khamis> copy attatched to <SN>/share/sourcenav/gui
Hi Khamis.
It is traditional to send bug fixes as context- or uni-diffs. Sending
replacement files is bad because it takes up a lot more bandwidth
(typically). Diffs are also superior because they let the maintainers
immediately see what has changed. Less work for maintainers means
that patches go in more quickly, and everybody is happier.
If you have SN checked out of cvs you can use "cvs diff -u" or "cvs
diff -c" to create a diff.
Otherwise you have to use "diff -u" or "diff -c" by hand (and remember
to keep the original around).
It's also good to write a ChangeLog entry and send it with the patch.
This also makes it easier for developers to check in patches (I don't
know about SN but on other projects I work on a ChangeLog entry is a
prerequisite to any commit).
I don't work on SN. I just happened to see two humongous email
messages in my inbox this morning and thought I would send email about
it.
Tom