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

Re: SVN Commit and Properties

From: Andy Levy <andy.levy_at_gmail.com>
Date: Mon, 17 Aug 2009 19:06:28 -0400

On Mon, Aug 17, 2009 at 18:29, BRM<bm_witness_at_yahoo.com> wrote:
> I was afraid that would be the answer.
> I think it would be beneficial to be able to do so though - or perhaps just be able to specify which files NOT to commit:
> $ svn commit -someFile.cpp
> or
> $ svn commit --skip-files someFile.cpp someOtherFile.cpp

Did you try the --non-recursive (or -N) switch?

You might have to do it in 2 stages:
svn ci --non-recursive
svn ci file1.cpp file2.cpp

Or this might even work (untested, I could be talking out of a
non-vocal orifice here):

svn ci --non-recursive . file1.cpp file2.cpp

> ----- Original Message ----
> From: Daniel Becroft <djcbecroft_at_gmail.com>
> To: users_at_subversion.tigris.org
> Cc: BRM <bm_witness_at_yahoo.com>
> Sent: Monday, August 17, 2009 6:20:17 PM
> Subject: Re: SVN Commit and Properties
> On Tue, Aug 18, 2009 at 7:47 AM, BRM <bm_witness_at_yahoo.com> wrote:
>> I have a project in SVN that uses svn:externals to bring in headers and libraries from other parts of the source tree.
>> Typically, I modify these and commit them with all the other files in the commit, so everything is okay.
>> However, I just had a situation where I didn't want to commit one of the files in my working copy, but I wanted to commit the property.
>> Normally, when I want to do a partial commit of the working copy I just specify the files on the command-line:
>> $ svn commit file1.cpp file2.cpp file3.h -m "some message"
>> However, using the dot operator (.) to specify the local copy for the properties also pulled in my other file.
>> Is there a way to specify the properties, such as svn:externals, to commit to be able to commit them without committing all the changes in the working copy?
>> Note: In case you are wondering, the file I didn't want to commit was a script that I had modified for my testing purposes, but really is of no value to others using the source. While it's okay it got committed, I would rather it not have. I'm more curious with this for future commits where I may have files that I really don't want committed yet. Sadly, I'm stuck with SVN 1.4 at the moment (due to server OS limitations).
> You simply need to commit the file/folder on which the properties have
> changed, in the same manner as specifying individual files to commit.
> However, you cannot differentiate between committing properties and
> commit file changes.
> Cheers,
> Daniel B.
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2384555
> To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-18 01:07:30 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.