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

RE: Is there excludes on implicit checkins?

From: Jay Glanville <jay.glanville_at_naturalconvergence.com>
Date: 2004-03-26 15:04:00 CET

> > Why do I want this? I have about 8 configuration files scattered
> > throughout my working copy of over 12,000 files. I am
> about to checkin
> > changes to over 65 of those files in 10 different
> subdirectories off of
> > root. I want all those 65 files to be in one 'changeset' or checkin
> > (i.e.: I need them to be atomic). However, there's 8 files
> that have
> > been modified that I don't want checked in, and these are the same 8
> > files that I don't want checked in next time.
> If you never want these 8 files to be checked in, why are they under
> version control in the first place? Just trying to understand your
> use-case here.

The properties file was stored in SCM because it's a deliverable part of
the system. I've modified it for my systems configuration. I just
don't want my modifications to be submitted. For example, the
properties file might have content looking like this:

   database.hostname = @DB_HOSTNAME@

The @DB_HOSTNAME@ would get replaced as part of the installation. In
order for me to connect to the database in my environment though, I need
to replace the @DB_HOSTNAME@ with 'db_service'.

Why don't I simply copy the properties file to myfoo.properties and use
that one? Because by modifying it while under revision control, the SCM
system will then tell me when I need to deal with other peoples changes
to the files, through the 'merge required' status.

> > Perhaps a future solution for this would be to be able to
> flag certain
> > files for checkin, or to be able to create a 'change set',
> and then add
> > and remove files from that change set.
> Actually, I've seen many GUI client designs that describe this exact
> sort of thing. I just don't know of any SVN GUIs that do this yet.

RapicSVN has something similar, in that you can flatten the file tree,
and then group by status.

I guess in some ways, I really want the concept of change sets. In
Perforce, I could create a change set, add the 8 files I didn't want to
submit to that change set and don't submit it. Therefore, when I would
create a second changeset and tell it to add all modified files to it,
it would skip over the files in the first change set, because they were
already flagged.


Jay Glanville
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Mar 26 15:05:34 2004

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