Date: Mon, 1 Dec 2008 11:23:40 +0300 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: Max Laier <max@love2party.net> Cc: freebsd-hackers@freebsd.org, kientzle@freebsd.org, perryh@pluto.rain.com Subject: Re: keeping track of local modifications Message-ID: <gFpinjQW6hEatbsT%2BXzE0kSsZf0@kjaK%2B/sQ5DW5981v71UogZJPf/0> In-Reply-To: <200812010830.17259.max@love2party.net> References: <4931CB02.9070904@gmail.com> <4932E8CF.9040501@freebsd.org> <49337f04.p8QqvfzTga07ypa6%perryh@pluto.rain.com> <200812010830.17259.max@love2party.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--RYJh/3oyKhIjGcML Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Max, good day. Mon, Dec 01, 2008 at 08:30:16AM +0100, Max Laier wrote: > On Monday 01 December 2008 07:07:00 perryh@pluto.rain.com wrote: > > * http://wiki.freebsd.org/LocalMercurial > > > > This seems less of a resource hog, and (if I am understanding > > matters correctly) is able to start from the installed /usr/src/... > > rather than requiring the would-be hacker to download a redundant > > instance, but I was concerned that the page may not be up to date > > with current FreeBSD development methodology (e.g. csup vs cvsup). >=20 > If you want to contribute back, this is *not* the way to go. Patches fro= m=20 > anything other than SVN and maybe CVS are mostly useless. May be I am missing something, but what's wrong with the patches from other VCS, providing that with Subversion you can exchange only by the plain diffs? Yes, Git/Mercurial patches should be applied with 'patch -p1', but that's all. Subversion has no notion simular to 'git format-patch' and 'git am', if I am not messing the things up, so the only way to exchange with others are the patches themselves. > The local hg/git > approach is nice if you are already familiar with hg or git and just want= to > keep some patch sets for yourself. If you are looking to keep/develop a = patch > set and eventually share it with the world, svn or svk is the way to go. The only issue I do see is about '$FreeBSD$', but plain Subversion clients shouldn't mess with it. If person has commit privileges to the FreeBSD repository, then yes, probably Subversion will be fine (but there are git-svn and hgsvn, so locally user can work with the different VCS even in this case). Do I missing some important thing here? Thanks! --=20 Eygene _ ___ _.--. # \`.|\..----...-'` `-._.-'_.-'` # Remember that it is hard / ' ` , __.--' # to read the on-line manual =20 )/' _/ \ `-_, / # while single-stepping the kernel. `-'" `"\_ ,_.-;_.-\_ ', fsc/as # _.-'_./ {_.' ; / # -- FreeBSD Developers handbook=20 {_.-``-' {_/ # --RYJh/3oyKhIjGcML Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkkznwwACgkQthUKNsbL7YgYrQCgnfotCgiiYTNdSr+KyZiUbSCK 0/MAn3g/00A5ogv8hQl5bzKjjHvViHVH =g+3G -----END PGP SIGNATURE----- --RYJh/3oyKhIjGcML--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?gFpinjQW6hEatbsT%2BXzE0kSsZf0>