| 2008-10-08 11:35:40 |
BjornW |
description |
In Subversion it is possible to export a tree and overwrite a previous tree. I would expect similar behavior from bzr.
USAGE:
I use bzr to develop webapps in a non-web directory. After I've made some changes I export the code to a web-enabled directory (this forces me to keep check on my changes). This means I'll export the code lots of times and I would prefer to overwrite previously exported code using an extra bzr argument. Previously I used Subversion which allowed me to do this using: svn export --force SOURCE DESTINATION. It would be very nice if bzr export would allow this as well.
See also svn help export for more info on the exact syntax of svn. |
In Subversion it is possible to export a tree and overwrite a previous tree. I would expect similar behavior from bzr.
USAGE:
I use bzr to develop webapps in a non-web directory. After I've made some changes I export the code to a web-enabled directory (this forces me to keep check on my changes). This means I'll export the code lots of times and I would prefer to overwrite previously exported code using an extra bzr argument. Previously I used Subversion which allowed me to do this using: svn export --force SOURCE DESTINATION. It would be very nice if bzr export would allow this as well.
See also svn help export for more info on the exact syntax of svn.
For now I use: bzr push --use-existing-dir but this copies the .bzr directory which I preferably would not like to put in the web enabled directory. |
|
