On Fri, 4 Apr 2008, James Kingston wrote: > On Thu, Apr 3, 2008 at 7:05 PM, Daniel Barkalow <barkalow@xxxxxxxxxxxx> wrote: > > /c/wd/cc> cd /c/cc > > /c/cc> git pull ../wd/cc > > > > But wouldn't that fail, because the files are read-only? > > Actually, I just tried and it worked beautifully. The directory is > writable, so git replaces rather than modifies the files. Then I can > use CCRC to search for hijacked files, check them out in one swoop > with the option to keep my modifications, then check them all in as a > group. Ah, yes, I guess that would work. Although I suspect that it would be annoying to recover if you failed to get the locks for any of them, since you're missing CC's expected path for conflict resolution. -Daniel *This .sig left intentionally blank* -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
