Greg Ercolano wrote: > Is there an easy way to do an 'svn update' that *overwrites* all > files instead of doing a 'conflict' or 'merge'? ie. more like a tar > extraction to write over all the source files with the latest release.
I'm not quite sure about it, but recently I got a prompt sometimes letting mit choose what to do with conflicts. Maybe a newer svn version or something else... > The man pages and 'svn help update' don't seem to give an indication. You can alway do an svn revert before svn update, or even after this partial update, and then another update. > Like many of you, I often hand-tweak fltk to add print statements > and stuff just to check things, but if left behind, this messes up > an 'svn update' by conflicting the files instead of overwriting them, > leaving me with a half-updated fltk, and causes weird bugs that > really aren't there. > > Unless one is particularly vigilant to see that single 'C' > (conflict) character go by in the voluminous output of an update, > you can miss it, and end up with a partial update that has to be > fixed by hand. After a bigger update, I always do an svn stat after the update and look for C in the first column. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
