8

I am investigating a way to commit all modified/added files via the command line with Subversion, excluding a provided black list. Is this possible?

If I have, say, 100 files I would like to commit, but interspersed with that list are seven files that I don't want to commit. Is there a way to say "commit all files excluding /path/to/file1.php, /path/to/file2.php, /path/to/file3.php", etc....

For example, I would have to do something like:

svn ci [list all files to commit in here] -m 'my commit message'

However, is there a better way to do it? I can't find anything documented regarding it.

Improve this question
0

3 Answers 3

Reset to default
7

There is no option to ignore files on-the-fly on commit. However, there are two approaches you can take:

  1. Use the changelists feature. This can help you create filters for the files that you do want to commit and only commit those. As changelists are created on the developer machine, your filters won't impact the general repository. For example, you can add all the files to a changelist using:

    svn changelist to-commit *

    And then remove those that you want to ignore:

    svn changelist --remove /path/to/file1.php

  2. Only svn add the files that you are working on, one by one as soon as you start editing one. Any file that has not been svn added to the repository will be ignored on commit. Of course, this comes with the disadvantage that you will be the only developer that will have those files on his machine.

Improve this answer
Sign up to request clarification or add additional context in comments.

5 Comments

Better will be to use --targets ARG : pass contents of file ARG as additional args on creating changelist stage
I guess that depends on the ratio between the number of files he wants to add vs the ones he want to exclude. Seeing how he only wants to exclude ~7 files out of ~100, I find it easier to add all of them to the changelist and then manually remove only the few that need to be ignored.
Yes, it depends, but for long lists file-source is just manageable, from my POV
Thanks, this is an interesting feature that I was not aware of. I'm sure it will come in use to me in the future. So, it would seem there is no way to create a blacklist or exclude list when performing an on-the-fly commit - that's a shame.
I'll accept your answer @VictorStanciu as it would appear there is no way to create a on-the-fly blacklist, certainly at this moment in time.
5

I had a similar situation where in I had to commit only certain files from a bunch of modified files. I had to update/remove a dependency from a parent and all of its child projects (Maven) and commit the corresponding changes. Here is what I did to create the SVN changelist.

svn cl my-changelist $(svn st | grep '^M' | awk '{print $2}' | grep 'pom.xml')

svn commit -m "Updated dependencies" --changelist my-changelist

The first command above creates a changelist with name 'my-changelist' and adds all the modified files with name 'pom.xml' to the list.

The second command commits the changelist (all the files in the list against a single revision number).

Improve this answer

Comments

0

You can use the Subversion svn:ignore property for this.

Improve this answer

1 Comment

The issue here is that I don't want to ignore those files forever, and I don't want to forget about them. It's like that i'll make my commit of my 90-odd files and then make some more changes to the other 7 then make a commit later that day or the following day. Applying an svn:ignore will ignore these files until told otherwise, AFAIK.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.