Re: Problems with uncommitted working directories, from home and work.

[ On Tuesday, December 2, 2003 at 18:04:35 (-0800), Mark D. Baushke wrote: ] Subject: Re: Problems with uncommitted working directories, from home and work. I suppose you could also consider the Unison File Synchronizer (see http://www.cis.upenn.edu/~bcpierce/unison/ for details) as a way

Re: Problems with uncommitted working directories, from home and work.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Greg A. Woods [EMAIL PROTECTED] writes: [ On Tuesday, December 2, 2003 at 18:04:35 (-0800), Mark D. Baushke wrote: ] Subject: Re: Problems with uncommitted working directories, from home and work. I suppose you could also consider the Unison

Problems with uncommitted working directories, from home and work.

Hi, I'm finding this problem a bit hard to explain in a few words, and aren't having much luck with search engines finding an answer. I work onsite about half the time and offsite the other half. Some nights, I'll be onsite, be half way through a complex set of changes, have heaps of modified

RE: Problems with uncommitted working directories, from home and work.

Craig O'Shannessy [mailto:[EMAIL PROTECTED] wrote: I work onsite about half the time and offsite the other half. Some nights, I'll be onsite, be half way through a complex set of changes, have heaps of modified files, and have to go home. The next morning, I want to pick up from where I

Re: Problems with uncommitted working directories, from home and work.

I can't commit the stuff at work (at least to the head branch), because it's not stable enough (may not even build). So the obvious answer is: use a branch to do your unstable commits! You should do that anyway, because it sounds to be that you are making changes that go uncommited for a long

Re: Problems with uncommitted working directories, from home and work.

I've applied two approaches to address this problem that can be implemented readily with CVS: The first method is to use a personal branch for your own development and periodically merge to the main branch. This is a standard pattern of use in CVS. The second is to divorce the notion of

Re: Problems with uncommitted working directories, from home and work.

[ On Wednesday, December 3, 2003 at 02:12:59 (+1100), Craig O'Shannessy wrote: ] Subject: Problems with uncommitted working directories, from home and work. I never had this problem before, I've been using ssh and vi for years, but now I'm addicted to an IDE (idea), so I've gotta find a better

Re: Problems with uncommitted working directories, from home and work.

On Tue, 2 Dec 2003, Greg A. Woods wrote: [ On Wednesday, December 3, 2003 at 02:12:59 (+1100), Craig O'Shannessy wrote: ] Subject: Problems with uncommitted working directories, from home and work. I never had this problem before, I've been using ssh and vi for years, but now I'm

Re: Problems with uncommitted working directories, from home and work.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Craig O'Shannessy [EMAIL PROTECTED] writes: The next best solution is to religiously use rsync to update your home machine's working directories and then always rsync your @home edits back to your work machine for any CVS operations which