From: Tom Tromey <tromey@redhat.com>
To: "Khamis Abuelkomboz (UUNET)" <khamis@knuut.de>
Cc: sourcenav@sources.redhat.com
Subject: Re: bug fix for goto problem
Date: Mon, 09 Apr 2001 12:09:00 -0000 [thread overview]
Message-ID: <87wv8tkhma.fsf@creche.redhat.com> (raw)
In-Reply-To: <3AD1DE49.7030500@knuut.de>
>>>>> "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
prev parent reply other threads:[~2001-04-09 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-09 9:08 Khamis Abuelkomboz (UUNET)
2001-04-09 12:09 ` Tom Tromey [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=87wv8tkhma.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=khamis@knuut.de \
--cc=sourcenav@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).