This might be a dumb question, but is there ANY elegant solution for keeping my Subversion repository in sync with my local files *including* adding files, deleting files, renaming files? I'm really trying to get religious about keeping all my projects under version control, but I find it such a pain in the arse to have to remember to do svn add, svn delete, svn rename whenever I decide to reorganize my project files. In every project I do, I always get to a point about halfway in where I say -- okay, this is messy -- let's combine these files, delete this one, and rename these more descriptively. Then my SVN repository gets all out of whack and refuses to let me make anymore commits, and that's the end of version control for that project. Happens every time.
Ideally: It would be so nice if I could sync my TM project to my SVN repository directly. If I rename something in the drawer, it gets renamed in the repository too. Delete files? Add files? Same thing. Is there some way to do this already? If not, how do you guys handle this issue? And if not, any chance of adding this functionality in a future release? Could a bundle be created to do this?
Sean
:::: DataFly.Net :::: Complete Web Services http://www.datafly.net
This might be a dumb question, but is there ANY elegant solution for keeping my Subversion repository in sync with my local files *including* adding files, deleting files, renaming files?
Something like this script might help with adds and deletes, but won't handle moves or renames:
http://svn.bitflux.ch/repos/public/bxcmsng/trunk/inc/bx/tools/svnsync
Chris
(Slightly hijacking the thread, and slightly off topic, sorry)
Can anyone point me to a definitive source for using SVN in web projects ?
I've tried it on my own several times and with a second developer once, but I still haven't found a good workflow or method.
This article is interesting, but too vague : http://www.sitepoint.com/blogs/2006/02/07/using-svn-for-web-development/
How do you guys handle SVN, and how have you integrated it in TM ?
My latest idea: using the auto-commit on save when you mount a webdav repository as a drive.
Thanks.
2006/2/25, Chris Thomas chris@cjack.com:
This might be a dumb question, but is there ANY elegant solution for keeping my Subversion repository in sync with my local files *including* adding files, deleting files, renaming files?
Something like this script might help with adds and deletes, but won't handle moves or renames:
http://svn.bitflux.ch/repos/public/bxcmsng/trunk/inc/bx/tools/svnsync
Chris
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Feb 25, 2006, at 1:17 AM, Ned Baldessin wrote:
(Slightly hijacking the thread, and slightly off topic, sorry)
Can anyone point me to a definitive source for using SVN in web projects ?
I've tried it on my own several times and with a second developer once, but I still haven't found a good workflow or method.
This article is interesting, but too vague : http://www.sitepoint.com/blogs/2006/02/07/using-svn-for-web- development/
How do you guys handle SVN, and how have you integrated it in TM ?
My latest idea: using the auto-commit on save when you mount a webdav repository as a drive.
Using WebDAV auto-commit is a good idea if you work only on static content, where the commit message and diff would give pretty much the same information anyway.
If you are developing web applications, however, I strongly recommend you do it the Right Way™. That is, set up a fully independent, development server on your machine. If, like me, you don't like the idea of messing around and installing low level stuff on your OS X box, have a look a "one click" solutions. For Rails, Locomotive [1] is excellent. For PHP/MySQL/Apache, I use xampp [2].
You can have the SVN repository either on your machine or on the server. I use the second option so I can make quick changes from other machines. Either way, backup the entire svn repos using svndump on the second machine. You can use incremental backups if your repository is really big.
When you work on the source, it's a good practice to commit your changes in small chunks. One commit per modification is ideal. More than one file can be modified, but try to commit the changes on a "feature" basis. You'll appreciate this extra work when you'll have different branches and want to merge, rollback or combine changesets without having to do it on a file by file basis.
One last thing. If you use Rails, here's something I discovered after a while: it's so quick easy to modify an application in Rails... I often forget to commit my changes regularly ! Then I end up with 20 modified files, related to around 4 different "iterations". Log messages can get tedious when such things happen.
I've used this setup with PHP applications, LaTeX, C++ projects, and now using it for a Rails application.
Ben
[1] http://locomotive.raaum.org/home/show/HomePage [2] http://www.apachefriends.org/en/xampp-macosx.html
Thanks.
2006/2/25, Chris Thomas chris@cjack.com:
This might be a dumb question, but is there ANY elegant solution for keeping my Subversion repository in sync with my local files *including* adding files, deleting files, renaming files?
Something like this script might help with adds and deletes, but won't handle moves or renames:
http://svn.bitflux.ch/repos/public/bxcmsng/trunk/inc/bx/tools/svnsync
Chris
_ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Not to hijack the thread or anything, but the way you formatted your email, did you do that on your own? I.e. the links.
I've noticed more and more people with emails like that (from other places too) and I was curious if you are automating it, or if your just doing it by hand.
(Im referring to ben and his [1] marks)
Regards,
Eric Coleman
On Feb 25, 2006, at 2:04 AM, Benoit Gagnon wrote:
On Feb 25, 2006, at 1:17 AM, Ned Baldessin wrote:
(Slightly hijacking the thread, and slightly off topic, sorry)
Can anyone point me to a definitive source for using SVN in web projects ?
I've tried it on my own several times and with a second developer once, but I still haven't found a good workflow or method.
This article is interesting, but too vague : http://www.sitepoint.com/blogs/2006/02/07/using-svn-for-web- development/
How do you guys handle SVN, and how have you integrated it in TM ?
My latest idea: using the auto-commit on save when you mount a webdav repository as a drive.
Using WebDAV auto-commit is a good idea if you work only on static content, where the commit message and diff would give pretty much the same information anyway.
If you are developing web applications, however, I strongly recommend you do it the Right Way™. That is, set up a fully independent, development server on your machine. If, like me, you don't like the idea of messing around and installing low level stuff on your OS X box, have a look a "one click" solutions. For Rails, Locomotive [1] is excellent. For PHP/MySQL/Apache, I use xampp [2].
You can have the SVN repository either on your machine or on the server. I use the second option so I can make quick changes from other machines. Either way, backup the entire svn repos using svndump on the second machine. You can use incremental backups if your repository is really big.
When you work on the source, it's a good practice to commit your changes in small chunks. One commit per modification is ideal. More than one file can be modified, but try to commit the changes on a "feature" basis. You'll appreciate this extra work when you'll have different branches and want to merge, rollback or combine changesets without having to do it on a file by file basis.
One last thing. If you use Rails, here's something I discovered after a while: it's so quick easy to modify an application in Rails... I often forget to commit my changes regularly ! Then I end up with 20 modified files, related to around 4 different "iterations". Log messages can get tedious when such things happen.
I've used this setup with PHP applications, LaTeX, C++ projects, and now using it for a Rails application.
Ben
[1] http://locomotive.raaum.org/home/show/HomePage [2] http://www.apachefriends.org/en/xampp-macosx.html
Thanks.
2006/2/25, Chris Thomas chris@cjack.com:
This might be a dumb question, but is there ANY elegant solution for keeping my Subversion repository in sync with my local files *including* adding files, deleting files, renaming files?
Something like this script might help with adds and deletes, but won't handle moves or renames:
http://svn.bitflux.ch/repos/public/bxcmsng/trunk/inc/bx/tools/ svnsync
Chris
__ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
_ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
I'm glad that this thread has inspired lots of related discussion but how about my original questions? ;-)
Am I the only one who can't seem to get with the program in terms of manually keeping my svn repository in sync with my local working copy? How do you guys deal with the situation I described where the time comes when you need to move files around, rename stuff, combine some files, delete no longer used files etc. ? How the heck do you guys keep your svn in sync?
Sean
On Feb 25, 2006, at 5:55 PM, Eric Coleman wrote:
Not to hijack the thread or anything, but the way you formatted your email, did you do that on your own? I.e. the links.
I've noticed more and more people with emails like that (from other places too) and I was curious if you are automating it, or if your just doing it by hand.
(Im referring to ben and his [1] marks)
Regards,
Eric Coleman
On Feb 25, 2006, at 2:04 AM, Benoit Gagnon wrote:
On Feb 25, 2006, at 1:17 AM, Ned Baldessin wrote:
(Slightly hijacking the thread, and slightly off topic, sorry)
Can anyone point me to a definitive source for using SVN in web projects ?
I've tried it on my own several times and with a second developer once, but I still haven't found a good workflow or method.
This article is interesting, but too vague : http://www.sitepoint.com/blogs/2006/02/07/using-svn-for-web- development/
How do you guys handle SVN, and how have you integrated it in TM ?
My latest idea: using the auto-commit on save when you mount a webdav repository as a drive.
Using WebDAV auto-commit is a good idea if you work only on static content, where the commit message and diff would give pretty much the same information anyway.
If you are developing web applications, however, I strongly recommend you do it the Right Way™. That is, set up a fully independent, development server on your machine. If, like me, you don't like the idea of messing around and installing low level stuff on your OS X box, have a look a "one click" solutions. For Rails, Locomotive [1] is excellent. For PHP/MySQL/Apache, I use xampp [2].
You can have the SVN repository either on your machine or on the server. I use the second option so I can make quick changes from other machines. Either way, backup the entire svn repos using svndump on the second machine. You can use incremental backups if your repository is really big.
When you work on the source, it's a good practice to commit your changes in small chunks. One commit per modification is ideal. More than one file can be modified, but try to commit the changes on a "feature" basis. You'll appreciate this extra work when you'll have different branches and want to merge, rollback or combine changesets without having to do it on a file by file basis.
One last thing. If you use Rails, here's something I discovered after a while: it's so quick easy to modify an application in Rails... I often forget to commit my changes regularly ! Then I end up with 20 modified files, related to around 4 different "iterations". Log messages can get tedious when such things happen.
I've used this setup with PHP applications, LaTeX, C++ projects, and now using it for a Rails application.
Ben
[1] http://locomotive.raaum.org/home/show/HomePage [2] http://www.apachefriends.org/en/xampp-macosx.html
Thanks.
2006/2/25, Chris Thomas chris@cjack.com:
This might be a dumb question, but is there ANY elegant solution for keeping my Subversion repository in sync with my local files *including* adding files, deleting files, renaming files?
Something like this script might help with adds and deletes, but won't handle moves or renames:
http://svn.bitflux.ch/repos/public/bxcmsng/trunk/inc/bx/tools/ svnsync
Chris
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
__ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
_ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Feb 25, 2006, at 8:39 AM, Sean Schertell wrote:
I'm glad that this thread has inspired lots of related discussion but how about my original questions? ;-)
Am I the only one who can't seem to get with the program in terms of manually keeping my svn repository in sync with my local working copy? How do you guys deal with the situation I described where the time comes when you need to move files around, rename stuff, combine some files, delete no longer used files etc. ? How the heck do you guys keep your svn in sync?
Unfortunately, you cannot use TextMate for these manipulations. I keep a Terminal window open at all time. There are a lot of things you can do within TextMate, however. You can create new files and add them to the repository, you can revert/update/diff files, etc. If you prefer a visual tool for the other commands, I suggest SvnX [1]. Use it exclusively as a repository browser, but it also integrates a working copy browser/editor.
I believe Allan has planned a deeper integration of the SVN bundle inside TextMate (ie. project drawer) in future versions, but I won't propagate rumors :)
ben
[1] http://www.lachoseinteractive.net/en/community/subversion/svnx/ features/
Sean
On Feb 25, 2006, at 5:55 PM, Eric Coleman wrote:
Not to hijack the thread or anything, but the way you formatted your email, did you do that on your own? I.e. the links.
I've noticed more and more people with emails like that (from other places too) and I was curious if you are automating it, or if your just doing it by hand.
(Im referring to ben and his [1] marks)
Regards,
Eric Coleman
On Feb 25, 2006, at 2:04 AM, Benoit Gagnon wrote:
On Feb 25, 2006, at 1:17 AM, Ned Baldessin wrote:
(Slightly hijacking the thread, and slightly off topic, sorry)
Can anyone point me to a definitive source for using SVN in web projects ?
I've tried it on my own several times and with a second developer once, but I still haven't found a good workflow or method.
This article is interesting, but too vague : http://www.sitepoint.com/blogs/2006/02/07/using-svn-for-web- development/
How do you guys handle SVN, and how have you integrated it in TM ?
My latest idea: using the auto-commit on save when you mount a webdav repository as a drive.
Using WebDAV auto-commit is a good idea if you work only on static content, where the commit message and diff would give pretty much the same information anyway.
If you are developing web applications, however, I strongly recommend you do it the Right Way™. That is, set up a fully independent, development server on your machine. If, like me, you don't like the idea of messing around and installing low level stuff on your OS X box, have a look a "one click" solutions. For Rails, Locomotive [1] is excellent. For PHP/MySQL/Apache, I use xampp [2].
You can have the SVN repository either on your machine or on the server. I use the second option so I can make quick changes from other machines. Either way, backup the entire svn repos using svndump on the second machine. You can use incremental backups if your repository is really big.
When you work on the source, it's a good practice to commit your changes in small chunks. One commit per modification is ideal. More than one file can be modified, but try to commit the changes on a "feature" basis. You'll appreciate this extra work when you'll have different branches and want to merge, rollback or combine changesets without having to do it on a file by file basis.
One last thing. If you use Rails, here's something I discovered after a while: it's so quick easy to modify an application in Rails... I often forget to commit my changes regularly ! Then I end up with 20 modified files, related to around 4 different "iterations". Log messages can get tedious when such things happen.
I've used this setup with PHP applications, LaTeX, C++ projects, and now using it for a Rails application.
Ben
[1] http://locomotive.raaum.org/home/show/HomePage [2] http://www.apachefriends.org/en/xampp-macosx.html
Thanks.
2006/2/25, Chris Thomas chris@cjack.com:
This might be a dumb question, but is there ANY elegant solution for keeping my Subversion repository in sync with my local files *including* adding files, deleting files, renaming files?
Something like this script might help with adds and deletes, but won't handle moves or renames:
http://svn.bitflux.ch/repos/public/bxcmsng/trunk/inc/bx/tools/ svnsync
Chris
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
__ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
_ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Feb 25, 2006, at 5:39 AM, Sean Schertell wrote:
How do you guys deal with the situation I described where the time comes when you need to move files around, rename stuff, combine some files, delete no longer used files etc. ? How the heck do you guys keep your svn in sync?
I just do it manually from the command line. Adding and deleting is pretty easy because SVN can handle recursion and wildcards. For instance, if I want to delete an entire directory and all the shell scripts in another, I can just do:
svn remove some-directory another-directory/*.sh
And if I want to see what files I need to add, I just do "svn status" and look for question marks. (The svn:ignore property can help if you find yourself distracted by persistent working copy files that don't belong in the repo.)
Moving and renaming isn't quite as simple, but these tasks should be fairly rare. If you find yourself doing lots of this, you probably didn't plan out your design well enough beforehand. Still, when you need to move or rename, doing so in Subversion isn't any more difficult than the Unix mv command.
Trevor
Hi Trevor,
Am 25.02.2006 um 18:27 schrieb Trevor Harmon:
How do you guys deal with the situation I described where the time comes when you need to move files around, rename stuff, combine some files, delete no longer used files etc. ? How the heck do you guys keep your svn in sync?
I just do it manually from the command line.
This is absolutely the way to work with svn. svn mv X, svn cp X Y, svn rm Z. It starts at the command line. Check the results, only then check in.
And I'd never want it automatically commit, nor automagically update. "svn up", "svn ci", that's at hard as it gets, and it should be a concious act.
And if I want to see what files I need to add, I just do "svn status" and look for question marks. (The svn:ignore property can help if you find yourself distracted by persistent working copy files that don't belong in the repo.)
Pray tell me, how do you set the svn:ignore property to exclude, say, all *.o files in a directory tree?
AFAIK this is stored with the repository, which of course is a good thing, so that your team mates won't accidentally check in things that don't belong in _that_ specific place of the repository, while *.o files may make perfect sense in your release database.
Oh, and sorry for turning TextMate into an svn forum. It shouldn't take long.
Regards, Peter Vohmann
On 2/25/06, Peter Vohmann pvohmann@mac.com wrote:
Hi Trevor,
Am 25.02.2006 um 18:27 schrieb Trevor Harmon:
How do you guys deal with the situation I described where the time comes when you need to move files around, rename stuff, combine some files, delete no longer used files etc. ? How the heck do you guys keep your svn in sync?
I just do it manually from the command line.
This is absolutely the way to work with svn. svn mv X, svn cp X Y, svn rm Z. It starts at the command line. Check the results, only then check in.
And I'd never want it automatically commit, nor automagically update. "svn up", "svn ci", that's at hard as it gets, and it should be a concious act.
And if I want to see what files I need to add, I just do "svn status" and look for question marks. (The svn:ignore property can help if you find yourself distracted by persistent working copy files that don't belong in the repo.)
Pray tell me, how do you set the svn:ignore property to exclude, say, all *.o files in a directory tree?
to set/edit: svn propedit svn:ignore .
to view: svn propget svn:ignore
to list all properties: svn proplist .
to remove: svn propdel
AFAIK this is stored with the repository, which of course is a good thing, so that your team mates won't accidentally check in things that don't belong in _that_ specific place of the repository, while *.o files may make perfect sense in your release database.
Oh, and sorry for turning TextMate into an svn forum. It shouldn't take long.
I think we need a propset command in the SVN bundle, so this had its place in the list :)
ben
Regards, Peter Vohmann
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
I skimmed the thread and didn't see this posted. But if anyone is reading this and wants to learn Subversion but doesn't know where to start, this is a great book, and it's free. I went through it in about 3 days an hour or so per day. It's a great way to learn SVN.
Kyle
On 2/25/06, Benoit Gagnon b.gagnon@gmail.com wrote:
On 2/25/06, Peter Vohmann pvohmann@mac.com wrote:
Hi Trevor,
Am 25.02.2006 um 18:27 schrieb Trevor Harmon:
How do you guys deal with the situation I described where the time comes when you need to move files around, rename stuff, combine some files, delete no longer used files etc. ? How the heck do you guys keep your svn in sync?
I just do it manually from the command line.
This is absolutely the way to work with svn. svn mv X, svn cp X Y, svn rm Z. It starts at the command line. Check the results, only then check in.
And I'd never want it automatically commit, nor automagically update. "svn up", "svn ci", that's at hard as it gets, and it should be a concious act.
And if I want to see what files I need to add, I just do "svn status" and look for question marks. (The svn:ignore property can help if you find yourself distracted by persistent working copy files that don't belong in the repo.)
Pray tell me, how do you set the svn:ignore property to exclude, say, all *.o files in a directory tree?
to set/edit: svn propedit svn:ignore .
to view: svn propget svn:ignore
to list all properties: svn proplist .
to remove: svn propdel
AFAIK this is stored with the repository, which of course is a good thing, so that your team mates won't accidentally check in things that don't belong in _that_ specific place of the repository, while *.o files may make perfect sense in your release database.
Oh, and sorry for turning TextMate into an svn forum. It shouldn't take long.
I think we need a propset command in the SVN bundle, so this had its place in the list :)
ben
Regards, Peter Vohmann
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On Feb 25, 2006, at 3:55 AM, Eric Coleman wrote:
Not to hijack the thread or anything, but the way you formatted your email, did you do that on your own? I.e. the links.
I've noticed more and more people with emails like that (from other places too) and I was curious if you are automating it, or if your just doing it by hand.
Oh, this is all manual work :) I got inspired by the Markdown syntax, DaringFireball website and other messages from this very list, but I believe it is a pretty common practice. I think it's a great presentational technique both for the writer and the reader. I will generally put all the [x] marks in the text as I write, then go on a quest to actually fetch the URLs for those links. That way I don't have to read again to see where I could fit them. As for the reader, she will usually read the entire email before clicking any link that would open a new window, change apps, etc. Having URLs at the very end of the message makes perfect sense in this context.
ben
(Im referring to ben and his [1] marks)
Regards,
Eric Coleman
On Feb 25, 2006, at 2:04 AM, Benoit Gagnon wrote:
On Feb 25, 2006, at 1:17 AM, Ned Baldessin wrote:
(Slightly hijacking the thread, and slightly off topic, sorry)
Can anyone point me to a definitive source for using SVN in web projects ?
I've tried it on my own several times and with a second developer once, but I still haven't found a good workflow or method.
This article is interesting, but too vague : http://www.sitepoint.com/blogs/2006/02/07/using-svn-for-web- development/
How do you guys handle SVN, and how have you integrated it in TM ?
My latest idea: using the auto-commit on save when you mount a webdav repository as a drive.
Using WebDAV auto-commit is a good idea if you work only on static content, where the commit message and diff would give pretty much the same information anyway.
If you are developing web applications, however, I strongly recommend you do it the Right Way™. That is, set up a fully independent, development server on your machine. If, like me, you don't like the idea of messing around and installing low level stuff on your OS X box, have a look a "one click" solutions. For Rails, Locomotive [1] is excellent. For PHP/MySQL/Apache, I use xampp [2].
You can have the SVN repository either on your machine or on the server. I use the second option so I can make quick changes from other machines. Either way, backup the entire svn repos using svndump on the second machine. You can use incremental backups if your repository is really big.
When you work on the source, it's a good practice to commit your changes in small chunks. One commit per modification is ideal. More than one file can be modified, but try to commit the changes on a "feature" basis. You'll appreciate this extra work when you'll have different branches and want to merge, rollback or combine changesets without having to do it on a file by file basis.
One last thing. If you use Rails, here's something I discovered after a while: it's so quick easy to modify an application in Rails... I often forget to commit my changes regularly ! Then I end up with 20 modified files, related to around 4 different "iterations". Log messages can get tedious when such things happen.
I've used this setup with PHP applications, LaTeX, C++ projects, and now using it for a Rails application.
Ben
[1] http://locomotive.raaum.org/home/show/HomePage [2] http://www.apachefriends.org/en/xampp-macosx.html
Thanks.
2006/2/25, Chris Thomas chris@cjack.com:
This might be a dumb question, but is there ANY elegant solution for keeping my Subversion repository in sync with my local files *including* adding files, deleting files, renaming files?
Something like this script might help with adds and deletes, but won't handle moves or renames:
http://svn.bitflux.ch/repos/public/bxcmsng/trunk/inc/bx/tools/ svnsync
Chris
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
__ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
_ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 25-Feb-06, at 7:07 AM, Benoit Gagnon wrote:
On Feb 25, 2006, at 3:55 AM, Eric Coleman wrote:
Not to hijack the thread or anything, but the way you formatted your email, did you do that on your own? I.e. the links.
Oh, this is all manual work :) I got inspired by the Markdown syntax, DaringFireball website and other messages from this very list, but I believe it is a pretty common practice. I think it's a great presentational technique both for the writer and the reader. I will generally put all the [x] marks in the text as I write, then go on a quest to actually fetch the URLs for those links. ...
I think I first noticed this notation in the Gentoo Linux weekly newsletter. My linux box has been neglected since I got my Mac, but I used to use mutt[1] (console mail client) for reading mail. Mutt also likes to KISS and pipes the messages to urlview[2] which is a small app to show you a numbered list of all the links in the message and launch your browser when you make selections. When the [xx] numbers match up with urlview's numbers (that is, _every_ link has to be numbered in the message) it makes it easy to find the link you want to visit out of the 30+ links in the newsletter (type the link # and enter). Seems to be a pretty useful convention. I have no clue where it started though.
[1] http://www.mutt.org [2] http://pdb.finkproject.org/pdb/package.php/urlview
On 25/02/2006, at 21:14, Sami Samhuri wrote:
[...] Seems to be a pretty useful convention. I have no clue where it started though.
It's of course very similar to e.g. LaTeX citing, and has been used in academic areas for a long time, at least.
-- Sune.
On Feb 24, 2006, at 10:17 PM, Ned Baldessin wrote:
This article is interesting, but too vague : http://www.sitepoint.com/blogs/2006/02/07/using-svn-for-web- development/
I disagree with the author's claim that it's necessary for all developers to work on the same server. It's not hard to set up Apache locally with the same configuration as everyone else. I don't think you have to jump through all the hoops that are recommended in the article.
How do you guys handle SVN, and how have you integrated it in TM ?
We put our repo on a centralized machine. Team members would check in changes, and the manager would periodically update from HEAD and to see how things are progressing and run some tests on the deployment server. It worked fine; I don't see anything "tricky" about using SVN for web development.
My latest idea: using the auto-commit on save when you mount a webdav repository as a drive.
I assume you're not talking about a shared repository, where auto- commit is really not a good idea. You should only commit stable changes -- manually -- and include a description of what the change is in case it breaks something.
Trevor
Subversion is a pretty easy concept. The latest copy of the source is on the server. each developer has his "own" copy of the code.
Every day, I update my code (svn update). We get emails after someone commits, and we generally know who's working on what before hand. If I see a commit on something I need to touch, i make sure they are done, do an update, make my changes and so on.
It's a huge time & life saver. YOu can keep track of who does what and when, and if you make a mistake, it's only a few minutes and you can revert the changes.
Eric Coleman
On Feb 25, 2006, at 2:16 AM, Trevor Harmon wrote:
On Feb 24, 2006, at 10:17 PM, Ned Baldessin wrote:
This article is interesting, but too vague : http://www.sitepoint.com/blogs/2006/02/07/using-svn-for-web- development/
I disagree with the author's claim that it's necessary for all developers to work on the same server. It's not hard to set up Apache locally with the same configuration as everyone else. I don't think you have to jump through all the hoops that are recommended in the article.
How do you guys handle SVN, and how have you integrated it in TM ?
We put our repo on a centralized machine. Team members would check in changes, and the manager would periodically update from HEAD and to see how things are progressing and run some tests on the deployment server. It worked fine; I don't see anything "tricky" about using SVN for web development.
My latest idea: using the auto-commit on save when you mount a webdav repository as a drive.
I assume you're not talking about a shared repository, where auto- commit is really not a good idea. You should only commit stable changes -- manually -- and include a description of what the change is in case it breaks something.
Trevor
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
To reply to the original question ...
This is VERY MUCH the same situation I'm in and matches my feelings on the matter.
I work as a "team" of one, so any rearrangements I make in my svn repository aren't going to disrupt anyone else's work. It might well be that I should have a better idea of where I'm going (or where IT'S going) when I start a project, but that often isn't the case.
I'm not afraid of the command line, but I rarely do much work there and don't come from a CLI background (unless you include my CP/M use of about 20 years ago!!). So the comment "when you need to move or rename, doing so in Subversion isn't any more difficult than the Unix mv command" [Trevor Harmon, Feb 25, 2006] doesn't help me much. I don't routinely work at the command line, so I don't feel very comfortable with mv and the like. I'm OK with doing "svn update" or "svn commit," (of course I can do those from within TextMate!). But for moving and renaming files I'd prefer to be able to use those yummy GUI things "click and type" and "drag it where I want it." :)
Also, when I do this type of "clean up" it isn't as simple as renaming or moving just a single file or folder. Instead, it's usually a rather significant bit of reorganizing. I find it far easier to do this if I can refer to a visual representation of what I'm doing. What I'd *like* to be able to to do is reorganize my subversion working copy visually and have the appropriate svn commands executed automatically in the background, or in a "batch," after I was satisfied with what I'd done.
As an aside: in a team environment it might be rather disruptive (!) to have this sort of reorganization of the repository happen simply because I changed things in my TextMate project drawer.
As I don't feel the need to rename and move files very often, I'd be satisfied with using a separate (visual) svn client. There are a few, most of which are BADLY undercooked... most went right into the trash after a 2 minute trial. I don't have an opinion on this one yet:
SmartSVN [1]. (The "Professional" version only) appears to claim to be able to let you move things visually and then it will do the required svn work. "Smart Move (automatic detection of possibly moved or renamed files)." I can't test this at the moment because I have my subversion repository on my local hard drive (I'm not using a server), and SmartSVN doesn't support the file:// protocol (ya... how "smart" is that?). A price of 49 USD / 41 EUR seems a bit steep simply to gain this convenience.
Then there is "scplugin" that supposedly integrates SVN activity into the Mac OS X Finder [2] but work on this appears to have been abandon in December 2004 (yes, that's a 14 months ago). For that matter, the book [3] doesn't appear to be in active development either. The site offers "1.1 final" and "1.2, nightly build" but the current version of subversion is 1.3 (released in January 2006). I don't know how much has changed, but the book looks to be, technically, two versions out of date. :(
Back to the main point... does anyone have a visual ("GUI") solution to this challenge?
[1] http://www.smartsvn.com/smartsvn/features.jsp [2] http://scplugin.tigris.org/ [3] http://svnbook.red-bean.com/
eo
On Feb 24, 2006, at 6:20 PM, Sean Schertell wrote:
This might be a dumb question, but is there ANY elegant solution for keeping my Subversion repository in sync with my local files *including* adding files, deleting files, renaming files? I'm really trying to get religious about keeping all my projects under version control, but I find it such a pain in the arse to have to remember to do svn add, svn delete, svn rename whenever I decide to reorganize my project files. In every project I do, I always get to a point about halfway in where I say -- okay, this is messy -- let's combine these files, delete this one, and rename these more descriptively. Then my SVN repository gets all out of whack and refuses to let me make anymore commits, and that's the end of version control for that project. Happens every time.
Ideally: It would be so nice if I could sync my TM project to my SVN repository directly. If I rename something in the drawer, it gets renamed in the repository too. Delete files? Add files? Same thing. Is there some way to do this already? If not, how do you guys handle this issue? And if not, any chance of adding this functionality in a future release? Could a bundle be created to do this?
Sean
On Feb 25, 2006, at 9:32 PM, Eric O'Brien wrote:
I work as a "team" of one, so any rearrangements I make in my svn repository aren't going to disrupt anyone else's work. It might well be that I should have a better idea of where I'm going (or where IT'S going) when I start a project, but that often isn't the case.
I'm not afraid of the command line, but I rarely do much work there and don't come from a CLI background (unless you include my CP/M use of about 20 years ago!!). So the comment "when you need to move or rename, doing so in Subversion isn't any more difficult than the Unix mv command" [Trevor Harmon, Feb 25, 2006] doesn't help me much.
Given the difficulty you're having, I don't see why you're so fixated on Subversion when you're the only one accessing the repository. Why not use a version-tracking backup utility like rdiff-backup? Then you can just do:
rdiff-backup source destination
All of the changes (including moves and renames) will then be taken care of automatically. It works over the Internet, and it can roll back changes to any earlier date, just like Subversion.
You can install it from the unstable tree in Fink.
Trevor
*chuckle*
It's not so much that I'm having "difficulty" with subversion as that I'd just like to be able to use a visual tool when I need to significant rearrange my files that are under version control. I believe a API for subversion has been published, so is there a technical reason not to expect a visual interface?
I don't know enough to be "fixated" on Subversion! Apparently CVS is "out" now and SVN is the heir... so that's what I grabbed onto. I may in the future be working on projects where I'm not the only one messing with things, so I'd like to keep that option open. I've never heard of rdiff-backup... I'll check it out.
Thanks!
eo
On Feb 25, 2006, at 10:52 PM, Trevor Harmon wrote:
On Feb 25, 2006, at 9:32 PM, Eric O'Brien wrote:
I work as a "team" of one, so any rearrangements I make in my svn repository aren't going to disrupt anyone else's work. It might well be that I should have a better idea of where I'm going (or where IT'S going) when I start a project, but that often isn't the case.
I'm not afraid of the command line, but I rarely do much work there and don't come from a CLI background (unless you include my CP/M use of about 20 years ago!!). So the comment "when you need to move or rename, doing so in Subversion isn't any more difficult than the Unix mv command" [Trevor Harmon, Feb 25, 2006] doesn't help me much.
Given the difficulty you're having, I don't see why you're so fixated on Subversion when you're the only one accessing the repository. Why not use a version-tracking backup utility like rdiff-backup? Then you can just do:
rdiff-backup source destination
All of the changes (including moves and renames) will then be taken care of automatically. It works over the Internet, and it can roll back changes to any earlier date, just like Subversion.
You can install it from the unstable tree in Fink.
Trevor
On Feb 26, 2006, at 12:09 AM, Eric O'Brien wrote:
I don't know enough to be "fixated" on Subversion! Apparently CVS is "out" now and SVN is the heir... so that's what I grabbed onto.
I still think you're using the wrong tool for the job. All you need is quick and easy version control for one user, and CVS and SVN are both overkill for that. Tools like rdiff-backup should make you much happier.
I may in the future be working on projects where I'm not the only one messing with things, so I'd like to keep that option open.
You can always switch to Subversion later. You can simply import your most recent changes into a repo when the time comes.
Trevor
Eric O'Brien <ericob@...> writes:
*chuckle*
It's not so much that I'm having "difficulty" with subversion as that I'd just like to be able to use a visual tool when I need to significant rearrange my files that are under version control. I believe a API for subversion has been published, so is there a technical reason not to expect a visual interface?
Definately try La Chose Interactives svnX. This does the job for me, handling moves etc fine. Some of the actions are a little oblique, but are explained from help.
[1] http://www.lachoseinteractive.net/en/community/subversion/svnx/features/
-
Benoit Gagnon -
Chris Thomas -
Eric Coleman -
Eric O'Brien -
Kyle Swank -
Ned Baldessin -
Peter Vohmann -
Sami Samhuri -
Sean Schertell -
stephen Hamilton -
Sune Foldager -
Trevor Harmon