Date: Mon, 17 Jun 2002 16:32:28 +0200 From: Sheldon Hearn <sheldonh@starjuice.net> To: Will Andrews <will@csociety.org> Cc: Kris Kennaway <kris@obsecurity.org>, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: Verbose commit messages (Re: cvs commit: ports/deskutils/kdepim3 Makefile distinfo pkg-plist ports/deskutils/kdepim3/files patch-icallangbind.c patch-parseholiday.y patch-vcc.y patch-vobject.c patch-y_tab.c ports/audio/arts Makefile distinfo ports/audio/kdemultimedia3 Makefile distinfo ...) Message-ID: <44830.1024324348@axl.seasidesoftware.co.za> In-Reply-To: Your message of "Sat, 15 Jun 2002 18:57:06 EST." <20020615235706.GE53809@squall.waterspout.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 15 Jun 2002 18:57:06 EST, Will Andrews wrote: > > Informative commit messages can be great, but please try and remember > > the repo bloat when you write long commit messages for commits which > > touch large numbers of files. > > > > This single commit added close to a megabyte to the ports repo. > > You're right. It takes too long to commit the update with the > individual ports, since there are usually hundreds of files > updated in each upgrade, not to mention that doing them > individually loses atomicity. So perhaps what I'll do next time > is just keep the first line and point to a changelog on a website. > And perhaps follow up to the commit message with the contents of > that changelog. I really like seeing this detail in CVS, but Kris has a point. Maybe you could use a one-liner for "all the files", including "see revision history for x11/kde for more detauls", and then the long message in a follow-up commit to x11/kde (or whatever the big daddy port for this is)? Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44830.1024324348>