summaryrefslogtreecommitdiff
path: root/source3/libsmb
diff options
context:
space:
mode:
authorLuke Leighton <lkcl@samba.org>1997-11-07 03:37:18 +0000
committerLuke Leighton <lkcl@samba.org>1997-11-07 03:37:18 +0000
commit029904995d27c4e765abf9334df34c399a535bea (patch)
tree449364c775b39967aa74a6a1dc62ce993a31fc26 /source3/libsmb
parentb9c6add64536e855156a00e32e5288486114e66e (diff)
downloadsamba-029904995d27c4e765abf9334df34c399a535bea.tar.gz
samba-029904995d27c4e765abf9334df34c399a535bea.tar.bz2
samba-029904995d27c4e765abf9334df34c399a535bea.zip
local time discrepancies between the date on my computer and the date on
chris' computer (probably about four minutes) meant that chris' commits didn't get downloaded when i did a cvs update. therefore, i did a cvs update; make proto; cvs commit, and still got problems. so, five minutes later, i do a cvs update, and _then_ chris' server.c and mangle.c mods get downloaded, and i have to do another make proto. this particular problem has hit us *really* badly in the past, because i was taking files home (onto a portable that i hadn't reset the time on since i went to the states) and then recopying them back onto the computer here. if i do this, i do a touch *.c *.h; cvs -t update. *then* a cvs commit. (This used to be commit edb9c52948159baa48d9decd253a401737bd5363)
Diffstat (limited to 'source3/libsmb')
0 files changed, 0 insertions, 0 deletions