[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: commit philosophy

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-03-30 00:18:43 CEST

On Thu, Mar 29, 2001 at 07:39:12AM -0600, Ben Collins-Sussman wrote:
>
> Philosophical question about commits.
>
> * Suppose I have a working copy at revision 3, and the head revision
> on the repository is 10.
>
> * Suppose a file "foo/bar/baz.c" has a local change. So lazily, I
> type 'svn ci foo/bar'.
>
> * However, suppose that baz.c has a sibling subdir, "foo/bar/bop/", at
> revision 5.
>
> Here's the issue: should my commit cause revision 5 of foo/bar/bop/ to
> be merged into the head revision?

Absolutely not.

> Or should it do *nothing* but
> create a new revision of baz.c?

Yes.

I'm with Tripp on this one. This is the only viable and sensible thing to
do. We don't want the client pulling old revs up to the latest tree.

CHeers,
-g

-- 
Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:26 2006

This is an archived mail posted to the Subversion Dev mailing list.