Date: Thu, 6 Apr 2006 09:14:10 +0100 (BST) From: Robert Watson <rwatson@FreeBSD.org> To: Pawel Jakub Dawidek <pjd@FreeBSD.org> Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/geom/eli g_eli.c src/sys/geom/gate g_gate.c g_gate.h src/sys/geom/mirror g_mirror.c src/sys/geom/nop g_nop.c src/sys/geom/raid3 g_raid3.c src/sys/geom/shsec g_shsec.c g_shsec.h src/sys/geom/stripe g_stripe.c g_stripe.h ... Message-ID: <20060406091224.K53552@fledge.watson.org> In-Reply-To: <200604052212.k35MCTje066272@repoman.freebsd.org> References: <200604052212.k35MCTje066272@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Apr 2006, Pawel Jakub Dawidek wrote: > Modified files: (Branch: RELENG_6) > sys/geom/eli g_eli.c > sys/geom/gate g_gate.c g_gate.h > sys/geom/mirror g_mirror.c > sys/geom/nop g_nop.c > sys/geom/raid3 g_raid3.c > sys/geom/shsec g_shsec.c g_shsec.h > sys/geom/stripe g_stripe.c g_stripe.h > sys/geom/zero g_zero.c > Log: > Sync with HEAD. When synchronizing a branch to another branch, it's helpful to include revision information, so that when reviewing a branch log later, it's possible to easily determine which revisions were merged and when, and easily answer questions like "Was revision X merged?". Generally I like also including the commit messages or a summary so that it's easy to tell what feature changes or fixes are going back, but the revision numbers are sufficient to recreate that moderately easily. Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060406091224.K53552>