Thus spake Juli Mallett <[EMAIL PROTECTED]>: > * De: Giorgos Keramidas <[EMAIL PROTECTED]> [ Data: 2003-01-31 ] > [ Subjecte: Re: Seat-belt for source upgrades from stable to current ] > > On 2003-01-30 21:38, David Schultz <[EMAIL PROTECTED]> wrote: > > > Thus spake Mike Makonnen <[EMAIL PROTECTED]>: > > > > Use the r version of the cvs commands (like cvs rlog and rdiff). They operate >on > > > > the repository remotely, so you don't need to have the files checked out >localy. > > > > > > That's a pretty good solution, and I use those occasionally. It > > > would be a perfect solution if there were an 'rupdate', so I don't > > > have to (cd /tmp; cvs co src/file/i/want.c) > > > && cp /tmp/src/file/i/want.c /where/i/want/it > > > && rm -rf /tmp/src > > > all the time. > > > > # cd /tmp > > # cvs -d 'repo magic' export -rHEAD src/file/i/want.c > > > > Does `cvs export' do the trick for you? > > Further, export -d somedir might be useful in this situation to get the > files where you want them, though sometimes -d does not DWIM, so I'm > not sure :)
That works when the revision has a symbolic tag associated with it, but export seems to be picky and won't do numeric revision numbers of particular files. I guess I could always go by date. And yes, -d is picky, too; you can't export into your working directory. Still, not bad... It doesn't address the entire problem I mentioned before, because I still want to do diffs between local revisions and the repository. This thread is just a subthread of the original thread in which I guess we're talking about how to do a 'cvs update' without a copy of the repository. (Sorry Giorgos, your idea actually works for updates, just not for the original question I was asking. I was confused. ENOSLEEP.) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
