Thanks Brane, no :) plain fact is that I didn't think that changing code I messed up within the branch and then fixed as significant.
I sort of see the branch as a semi-private space, where I do stuff that you can look at, but that doesn't have much meaning (hence me terming N changes in M files as 'trivial' -- it's jst a bit of of umm ascii) until it's good and ready for me to invite scrutiny. Privacy for patzers :) Maybe what is needed is a personal commit space where I can reign supreme. (fact is, my computer is ancient (but nice and familiar to use) and I don't trust it.) My other problem is that Apache code carries a copyright, so I'm reluctant to use newfangled things like clouds and their fancy (loooong) usage legalese that could get me (and Apache) into trouble. (some ppl just like to see the world burn and the lawyers earn). I also hope not to give ppl too much useless work, hence me leaving off certain log messages off b/c they really are a waste of human time, it's just where I goofed and not worth anyone's time. That's the main concept here, I'm trying to save your time, probably in the wrong way :) Gabriela On Sun, Nov 17, 2013 at 8:19 PM, Branko Čibej <br...@wandisco.com> wrote: > On 17.11.2013 21:08, Gabriela Gibson wrote: > > Thank you Ivan, > > I was blithely assuming that because I was removing trivial changes I > introduced to the branch, that no-one would track them :) Also I was > trying to avoid writing trivial things for people to read. > > The log message is fixed now. > > Now I'm curious -- what tools do people use to revise patches that allow > them to instantly spot (seemingly) minor additions? > > > Do you mean "revise patches" or "review commits"? If it's the latter, the > fact that the list of affected files in the log message and the > automatically generated list of changes in the commit mail are different is > an obvious hint that something was either left out of the log message, or > inadvertently committed. > > -- Brane > > > -- > Branko Čibej | Director of Subversion > WANdisco // Non-Stop Data > e. br...@wandisco.com >