If I tie a plugin to SVN with the -x switch, won’t that mean the plugin
will get updated everytime the author checks in a new version of the
plugin?
TIA
Jeroen
If I tie a plugin to SVN with the -x switch, won’t that mean the plugin
will get updated everytime the author checks in a new version of the
plugin?
TIA
Jeroen
Yes, typically you will only want to do this with sources you trust.
[email protected] wrote:
Yes, typically you will only want to do this with sources you trust.
It would also be a bad idea to do this with a production app.
_Kevin
2006/9/6, _Kevin [email protected]:
[email protected] wrote:
Yes, typically you will only want to do this with sources you trust.
It would also be a bad idea to do this with a production app.
Which is where Piston comes in: http://piston.rubyforge.org/
Piston is a command line utility I wrote to manage vendor branches.
François Beausoleil
http://blog.teksol.info/
http://piston.rubyforge.org/
François Beausoleil wrote:
2006/9/6, _Kevin [email protected]:
[email protected] wrote:
Yes, typically you will only want to do this with sources you trust.
It would also be a bad idea to do this with a production app.
Which is where Piston comes in: http://piston.rubyforge.org/
Piston is a command line utility I wrote to manage vendor branches.
Looks nice! Isn’t this something should (and maybe is!) be available in
Subversion?
Jeroen
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs