summaryrefslogtreecommitdiff
path: root/e2/967b468b9b136ebff1b45f11861579ab63fd05
blob: e621169075d11b72e27f7aa9159dc35548dc0fd2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
	helo=mx.sourceforge.net)
	by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1VS3cu-0002jt-NG
	for bitcoin-development@lists.sourceforge.net;
	Fri, 04 Oct 2013 11:32:56 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.214.48 as permitted sender)
	client-ip=209.85.214.48; envelope-from=mh.in.england@gmail.com;
	helo=mail-bk0-f48.google.com; 
Received: from mail-bk0-f48.google.com ([209.85.214.48])
	by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1VS3cr-0002bE-UC
	for bitcoin-development@lists.sourceforge.net;
	Fri, 04 Oct 2013 11:32:56 +0000
Received: by mail-bk0-f48.google.com with SMTP id my13so1464307bkb.35
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 04 Oct 2013 04:32:47 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.205.22.71 with SMTP id qv7mr12510787bkb.20.1380886367374;
	Fri, 04 Oct 2013 04:32:47 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.204.237.74 with HTTP; Fri, 4 Oct 2013 04:32:47 -0700 (PDT)
In-Reply-To: <3552695.aET6a1zFq8@momentum>
References: <CANEZrP1Sd8cK2YUr4OSvnOxEJrbWpmfdpor-qbap1f98tGqPwg@mail.gmail.com>
	<3552695.aET6a1zFq8@momentum>
Date: Fri, 4 Oct 2013 13:32:47 +0200
X-Google-Sender-Auth: yjwFgfMYODWSnX2XezPTe5QLATY
Message-ID: <CANEZrP1-4vP10w6_Yg3tXAKcMh406rw2bsAnvML2WoaU5SUjYw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Andy Parkins <andyparkins@gmail.com>
Content-Type: multipart/alternative; boundary=20cf30223bf567533904e7e8a97e
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1VS3cr-0002bE-UC
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Code review
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 04 Oct 2013 11:32:56 -0000

--20cf30223bf567533904e7e8a97e
Content-Type: text/plain; charset=UTF-8

> There is more to a git branch than just the overall difference.  Every
> single
> log message and diff is individually valuable.


When the log messages don't accurately describe the contents of the diff,
it's just misinformation and noise. Everyone starts out by wanting a neat
collection of easy to understand and review commits, but in practice it's
extremely hard to always get it.

I know how to make squashed commits, thanks. I've done LOTS of code review
in my life. I'm making a point here as one of the few people who goes
through large pull requests and reviews them line by line. It's hard,
partly because github sucks, and partly because reviewing lots of small
commits sucks.

There's nothing that makes a single large commit harder to review. It's the
same amount of code or strictly less, given the tendency for later commits
to change earlier ones. You can easily search the entire change whilst
reviewing. There are lots of things that make it easier.

FWIW inside Google the code review process is one-commit-one-review.

--20cf30223bf567533904e7e8a97e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><div class=3D"im"><span style=3D"=
color:rgb(34,34,34)">There is more to a git branch than just the overall di=
fference. =C2=A0Every single</span><br>
</div>
log message and diff is individually valuable.</blockquote><div><br></div><=
div>When the log messages don&#39;t accurately describe the contents of the=
 diff, it&#39;s just misinformation and noise. Everyone starts out by wanti=
ng a neat collection of easy to understand and review commits, but in pract=
ice it&#39;s extremely hard to always get it.</div>
<div><br></div><div>I know how to make squashed commits, thanks. I&#39;ve d=
one LOTS of code review in my life. I&#39;m making a point here as one of t=
he few people who goes through large pull requests and reviews them line by=
 line. It&#39;s hard, partly because github sucks, and partly because revie=
wing lots of small commits sucks.</div>
<div><br></div><div>There&#39;s nothing that makes a single large commit ha=
rder to review. It&#39;s the same amount of code or strictly less, given th=
e tendency for later commits to change earlier ones. You can easily search =
the entire change whilst reviewing. There are lots of things that make it e=
asier.</div>
<div><br></div><div>FWIW inside Google the code review process is one-commi=
t-one-review.</div></div></div></div>

--20cf30223bf567533904e7e8a97e--