Without starting an IDE war, you might want to check out IDEA.  It has a
feature for shelving changes, which I've found incredibly useful in the
absence of local commits.  It basically creates a patch of a changeset that
it manages internally and can reapply at any time.  While it sounds simple
enough, it's done very well and has saved me a lot of hassle.

-- 
Kevin


On 4/28/08 2:55 PM, "Andrus Adamchik" <[EMAIL PROTECTED]> wrote:

> There is still no write SVN access, so we can't tag the release and
> will have to wait. There was a RAID failure and now while the
> replacement machine is being setup, all access is read-only.
> 
> And as it often happens, I started on a big new development on the eve
> of the release (CAY-929, CAY-560). And I honestly didn't mean to
> include that in M4 (i.e. the plan was to wait with this commit till
> after we tag the release)... But if I finish it during the SVN
> downtime, we might as well put it in the release.
> 
> CAY-929 (the modern join syntax for SelectQuery) is already finished
> and now I am adding the OUTER join semantics to expressions. I am not
> used to keep so many unrelated changes uncommitted and without
> multiple clear rollback points, but I guess I'll survive it that time...

Reply via email to