[tahoe-lafs-trac-stream] [tahoe-lafs] #1992: warn if testing uncommitted code

[tahoe-lafs]

#1992: warn if testing uncommitted code
------------------------------------+------------------------------------
     Reporter:  daira               |      Owner:  warner
         Type:  defect              |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  1.10.0
   Resolution:                      |   Keywords:  test git review-needed
Launchpad Bug:                      |
------------------------------------+------------------------------------

Comment (by zooko):

 Replying to [comment:4 gdt]:
 > I'm not Brian, but I think the notion that one prepares a commit and
 then tests it is sound.  So the tests warning that the source tree is
 dirty is a good idea.

 Thanks, gdt! It sounds like a pretty good idea to me, too. I think a lot
 of people get misdirected by git's terminology of calling a version a
 "commit". There is no ''commitment'' involved. You can change your mind at
 any time. ☺ Now a {{{git push}}}, to a repository that other people can
 read, now that's commitment. Even then it might not be a big deal if you
 are pushing to a repo+branch which everyone knows can get clobbered at any
 time.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1992#comment:5>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage