[01:06:47] --- Russ has left: Disconnected [03:15:40] --- haba has become available [05:37:35] --- Jeffrey Altman has left: Replaced by new connection [05:41:53] --- kula has become available [07:58:32] --- Jeffrey Altman has become available [08:23:02] --- cclausen has become available [09:16:13] --- matt has left [09:21:24] --- dev-zero@jabber.org has become available [09:27:51] --- dev-zero@jabber.org has left: Lost connection [11:13:26] --- Russ has become available [12:52:34] --- deason has become available [13:12:17] s/ioctl/pioctl/ [13:12:17] --- summatusmentis has left: Lost connection [13:16:51] --- summatusmentis has become available [13:27:34] --- dev-zero@jabber.org has become available [13:29:43] --- edgester has become available [13:30:59] Is http://docs.openafs.org/ReleaseNotesWindows/ support to have the latest release notes for windows? [13:31:18] Should I use that URL in the docs? [14:17:44] it does and you can [14:18:16] thanks! [14:18:54] The revision history seems wrong: Revision 1.5.6000 [14:19:19] What's wrong with that? [14:19:33] I just checked it and I get 1.5.6200 [14:46:12] I did a shift-refresh and got the right thing. Thanks [14:46:28] what doc are you working on? [15:05:41] admin Guide [15:06:23] --- dev-zero@jabber.org has left [15:40:07] Was is good practice to break up the commits like I did for the admin guide? [15:41:08] I don't think that level of breakup was required [15:41:27] one commit for the admin guide chapter three would have been sufficient. [15:43:05] breaking up commits is important when it would be hard to review the change (either due to the size) or the impact of the change (due to the scale) or when it might be the case that one portion of the change would be accepted and the rest denied. I don't think that is the case with the documentation changes you are making. [15:44:56] If you were doing an invasive, repetitive change like chaning all uses of "SHALL" to "WILL" across all of the documentation, or reindenting everything, I'd expect that to be separate from anything that actually makes substantive content changes. [15:46:15] Or, if we thought we were going to maintain separate documentation for 1.4 and 1.5/1.6/2.0/whatever, then you'd want changes which document behavior only present in the latter to be separate from changes which document behavior present in both, to make it possible to cherry-pick the right changes for the 1.4 docs. [16:38:26] ok, thanks. the patch for chp2 two was so big, that I over-compensated by breaking things up by subsection. [18:10:16] --- edgester has left [19:09:13] --- cclausen has left [20:42:11] --- cclausen has become available [21:15:22] --- brantgurga has become available [21:16:18] --- dev-zero@jabber.org has become available [21:23:11] --- deason has left [22:35:19] --- reuteras has become available [23:33:24] --- brantgurga has left [23:41:18] --- dev-zero@jabber.org has left