Date: Sun, 24 Jun 2007 17:10:31 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Pav Lucistnik <pav@FreeBSD.org> Cc: cvs-ports@FreeBSD.org, Joe Marcus Clarke <marcus@FreeBSD.org>, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/graphics/cairo Makefile ports/graphics/cairo/files patch-git Message-ID: <20070624171030.GA8036@FreeBSD.org> In-Reply-To: <1182701547.14601.6.camel@ikaros.oook.cz> References: <200706230010.l5N0AYKJ055836@repoman.freebsd.org> <20070624150141.GA85107@FreeBSD.org> <1182701547.14601.6.camel@ikaros.oook.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Jun 24, 2007 at 06:12:27PM +0200, Pav Lucistnik wrote: > Alexey Dokuchaev p??e v ne 24. 06. 2007 v 15:01 +0000: > > On Sat, Jun 23, 2007 at 12:10:34AM +0000, Joe Marcus Clarke wrote: > > > marcus 2007-06-23 00:10:34 UTC > > > Add a patch from Freedesktop git to fix a crash with OpenOffice > > > applications. > > > > > > Obtained from: Freedesktop git > > > > > > Revision Changes Path > > > 1.28 +1 -1 ports/graphics/cairo/Makefile > > > 1.1 +72 -0 ports/graphics/cairo/files/patch-git (new) > > > > It's usually a better practice to name such patches like > > `patch-ooo-crash-fix' instead. Mere `-git' suffix does not tell much > > about what is this patch for. > > Commit log says what the patch is for. True. It's just that in my example, digging for commit log is not necessary (but still, of course, advised). ./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070624171030.GA8036>