[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdepim-users
Subject:    [kdepim-users] Re: Submitting a patch
From:       Ingo =?windows-1252?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2004-03-31 0:05:21
Message-ID: 200403310205.21897 () erwin ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Tuesday 30 March 2004 19:31, Nathan Toone wrote:
> If I were to fix a bug in CVS, how would I go about submitting the
> patch so it can be included?
>
> Specifically, how do I create the diff file for the patch itself?

This was already explained. I just want to add that you should add the 
line
 diff -u3 -p
to your ~/.cvsrc file.
Then you can use
 cvs diff names_of_changed_files >meaningful_name.diff
to create the patch. If you didn't make several unrelated changes then 
you can omit the names of the changed files.

> Do I just upload it to the same bug?

I'd say that depends. At least in case of a KMail related patch it's 
better to send the patch to the corresponding developer's mailing-list 
(i.e. kmail-devel@kde.org) instead of attaching it to the bug report. 
It will get more attention this way.

Regards,
Ingo

[Attachment #5 (application/pgp-signature)]

_______________________________________________
KDE PIM users mailing list
kdepim-users@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users


[prev in list] [next in list] [prev in thread] [next in thread]