commit all files except a selected few?
Does subversion support any command line wizardry that offers the user a way to commit the changes made to all files under version control except those made to a selected few? Thanks, -- Zé
Re: Push ?
Guten Tag Dan White, am Sonntag, 15. September 2013 um 01:22 schrieben Sie: > Is is possible to push a checkout or update from a subversion server to a > remote client ? As said, there's no such mechanism in Subversion, but if you describe your problem more detailed, one can suggest workarounds. For example it shouldn't be a problem to login using ssh and initiate a client side update. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: commit all files except a selected few?
On Sun, Sep 15, 2013 at 6:10 AM, Zé wrote: > Does subversion support any command line wizardry that offers the user a way > to commit the changes made to all files under version control except those > made to a selected few? If you organize your files into changelists[1], you can commit a specific changelist and exclude other files. Other than that, svn commit allows you to pass multiple files/paths to be committed. You can specify individual paths and/or use your shell to pattern-match or glob files which should then be expanded by your shell to pass to svn. 1: http://svnbook.red-bean.com/en/1.7/svn.advanced.changelists.html
Re: commit all files except a selected few?
On 09/15/2013 12:31 PM, Andy Levy wrote: On Sun, Sep 15, 2013 at 6:10 AM, Zé wrote: Does subversion support any command line wizardry that offers the user a way to commit the changes made to all files under version control except those made to a selected few? If you organize your files into changelists[1], you can commit a specific changelist and exclude other files. That wouldn't really apply to this use case, as it relies on pre-established lists of related files. Other than that, svn commit allows you to pass multiple files/paths to be committed. You can specify individual paths and/or use your shell to pattern-match or glob files which should then be expanded by your shell to pass to svn. That doesn't apply as well, as the objective would be to easily exclude a single file, or a small subset of files, from an arbitrarily long list of files. Thanks anyway, Zé
Re: commit all files except a selected few?
On 09/15/2013 02:39 PM, Zé wrote: On 09/15/2013 12:31 PM, Andy Levy wrote: Other than that, svn commit allows you to pass multiple files/paths to be committed. You can specify individual paths and/or use your shell to pattern-match or glob files which should then be expanded by your shell to pass to svn. That doesn't apply as well, as the objective would be to easily exclude a single file, or a small subset of files, from an arbitrarily long list of files. Silly me. The answer is, quite obviously, in specifying glob patterns, particularly one which excludes a file. With bash, the !(excluded) glob pattern does just that. So, thanks to bash, the following command excludes main.c++ from a commit: $ svn commit -m "committing everything except main.c++" !(main.c++) Once again, a little knowledge of the shell goes a long way. Zé
Re: Push ?
The issue is that the client end of the transaction is in a DMZ A connection from a DMZ to one’s internal network is a very high security risk. What I was hoping for was a way to define a very specific connection from the Subversion server to the DMZ client (push). This is considered to be a much lower security risk. Searching for a solution found one possibility: Check out a copy on the subversion server and then rsync to the final client destination. I was hoping to find a one-step solution rather than a two step. Other considerations include using svnsync to create a copy in the DMZ, but that has its own security concerns. Sadly, this is not a simple problem. On Sep 15, 2013, at 6:21 AM, Thorsten Schöning wrote: > Guten Tag Dan White, > am Sonntag, 15. September 2013 um 01:22 schrieben Sie: > >> Is is possible to push a checkout or update from a subversion server to a >> remote client ? > > As said, there's no such mechanism in Subversion, but if you describe > your problem more detailed, one can suggest workarounds. For example > it shouldn't be a problem to login using ssh and initiate a client > side update.
Re: Push ?
Guten Tag Dan White, am Sonntag, 15. September 2013 um 17:32 schrieben Sie: > Searching for a solution found one possibility: Check out a copy on > the subversion server and then rsync to the final client destination. How is rsync more secure than accessing the client using SSH and use svn update? SSH has some options to limit access and possibilities. For example ForceCommand sounds interesting: http://askubuntu.com/questions/48129/how-to-create-a-restricted-ssh-user-for-port-forwarding > I was hoping to find a one-step solution rather than a two step. How about polling on the client? Issueing a svn update every some seconds shouldn't hurt client and server much. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail:thorsten.schoen...@am-soft.de AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...05151- 9468- 55 Fax...05151- 9468- 88 Mobil..0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Push ?
On 15.09.2013 01:22, Dan White wrote: > Is is possible to push a checkout or update from a subversion server to a > remote client ? You could try svnpubsub: http://svn.apache.org/viewvc/subversion/trunk/tools/server-side/svnpubsub/ It includes a client implementation called "svnwcsub" which does more or less what you need. Svnpubsub is included in the Subversion 1.8.x source tarballs. -- Brane -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
