Date: 13 Aug 2001 14:44:37 +0200 From: Thomas Gellekum <tg@melaten.rwth-aachen.de> To: Sheldon Hearn <sheldonh@starjuice.net> Cc: freebsd-ports@FreeBSD.ORG Subject: Re: cvs commit: ports/mail/gnumail Makefile distinfo pkg-plist ports/mail/gnumail/files patch-..:Headers:AddressBookController.h patch-..:Headers:EditWindowController.h patch-..:Headers:MailboxManagerController.h patch-..:Headers:NewAddressPanelController.h Message-ID: <kqofpkqgcq.fsf@cip12.melaten.rwth-aachen.de> In-Reply-To: Sheldon Hearn's message of "Thu, 09 Aug 2001 15:50:01 %2B0200" References: <32512.997365001@axl.seasidesoftware.co.za>
next in thread | previous in thread | raw e-mail | index | archive | help
Sheldon Hearn <sheldonh@starjuice.net> writes: > On Thu, 09 Aug 2001 04:06:25 MST, Thomas Gellekum wrote: > > > Modified files: > > mail/gnumail Makefile distinfo pkg-plist > > Added files: > > mail/gnumail/files patch-..:Headers:AddressBookController.h > > What's going on with these patch names? Have you seen the way patch > names are normally constructed? Define `normal'. Last time we had this discussion there was no definite conclusion and I've been using these names for months now. I prefer some information in the filename, so I'm using `patch-<the file to patch with / replaced by :>'. I can also imagine using something like e. g. `patch-os.statvfs' for a patch set (diffs to several files) that adds os.statvfs support to Python. I never really liked the old `patch-[a-z][a-z]', it's not intuitive. tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?kqofpkqgcq.fsf>