From kde-core-devel  Sat Jul 22 22:24:05 2006
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Sat, 22 Jul 2006 22:24:05 +0000
To: kde-core-devel
Subject: Re: kdelibs coding style
Message-Id: <200607221624.05424.aseigo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=115360828511229
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart12967039.x8U9xvHgfB"

--nextPart12967039.x8U9xvHgfB
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Thursday 20 July 2006 15:26, Reinhold Kainhofer wrote:
> Am Donnerstag, 20. Juli 2006 23:13 schrieb Jaison Lee:
> > I wonder tho; is a mass reindent entirely out of the question? It's
> > only one module (yes, the most important). We could do it right after
> > a monday, so most big commits will (hopefully) have been checked in.
>
> The problem is that this practically removes all history from svn blame, =
so
> you won't have an easy way to see who last changed a given piece of code.
>
> And particularly for a library, this is a really important functionality.

exactly. consensus was such a mass reindent would be a bad thing. in 1-2=20
year's time we'll probably have a pretty consistent code base. we can affor=
d=20
to take the long view here.

=2D-=20
Aaron J. Seigo
Undulate Your Wantonness
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

=46ull time KDE developer sponsored by Trolltech (http://www.trolltech.com)

--nextPart12967039.x8U9xvHgfB
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)

iD8DBQBEwqWF1rcusafx20MRAlgPAJ9IU/HdqzT/Oyv5p5pNSN6oiB2+igCdHff9
Y9w74sWMwZVeiYvaUZta8Zk=
=igEh
-----END PGP SIGNATURE-----

--nextPart12967039.x8U9xvHgfB--