Date: Sun, 07 Jul 2013 22:14:40 +0200 From: Gabor Kovesdan <gabor@FreeBSD.org> To: =?ISO-8859-1?Q?Ren=E9_Ladan?= <rene@freebsd.org> Cc: FBSD Doc project <doc@FreeBSD.org> Subject: Re: [CFT] merging projects/entities Message-ID: <51D9CC30.7090604@FreeBSD.org> In-Reply-To: <51D9BAD0.6000904@freebsd.org> References: <51D7F70B.8000206@freebsd.org> <51D83F92.7030808@FreeBSD.org> <51D98705.4070403@freebsd.org> <51D988DE.2050600@FreeBSD.org> <51D98E6D.2060306@freebsd.org> <51D99892.3000905@FreeBSD.org> <51D99D07.1070808@freebsd.org> <51D9B744.8040004@FreeBSD.org> <51D9BAD0.6000904@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Em 07-07-2013 21:00, René Ladan escreveu: > Heh, missed that myself too. So now only tidying up or synchronizing > whitespace for share/xml/catalog.xml remains to be done? Personally, I think it would be better to commit that whitespace fix separately. Even if you committed it separately in the branch, it would go to head intermixed with real changes, which makes it hard to read the backlog. This is a disadvantage in general and it is quite a big hassle for translators. I think you did it fine since you didn't have to foresee these consequences but maybe we should document it as a best practice to avoid whitespace changes in branches. Gabor
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51D9CC30.7090604>