www-infrastructure-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Erenkrantz" <jus...@erenkrantz.com>
Subject Re: [scm] Use case: Offline commit
Date Thu, 28 Feb 2008 15:51:42 GMT
On Wed, Feb 27, 2008 at 5:39 PM, Jukka Zitting <jukka.zitting@gmail.com> wrote:
>  Currently the best way to achieve this would be to use "svn diff" and
>  "svn revert" to create a patch for the change and to restore the
>  working copy to a baseline state for the next issue. Once back online,
>  the committer would apply and commit all such patches. While
>  reasonably usable, this solution doesn't work very well with
>  overlapping changes.

You might be interested in taking a look at the 'changelist' support
introduced in SVN 1.5.  It isn't perfect - as it suffers from the
overlapping change issue as well.  It's modeled after Perforce's
changelist support which likewise is file-based rather than
hunk-based.  However, it'd help a little bit in this situation.

Offline commits have been talked about before for SVN, and some
developers have an idea how to implement it.  But, that's probably
pretty far off unless someone steps up.  =)  -- justin

Mime
View raw message