Re: issue tracking, code diff/review
(2011/03/22 12:33), bruce wrote: Hi. I've got a basic workflow app that allows users to manage software apps, for different roles. For the "review" role, I'm trying to find a simple issue tracking app/code diff/review app that I can modify, to hook into what I'm creating. I've started looking into mantis/indefero, etc... Redmine can do that It is highly configurable/customizable project software management written in Ruby. http://www.redmine.org/ Code Review Plugin http://www.redmine.org/boards/3/topics/5878 Redmine supports svn integration natively Diff/review enabled by default User roles: Natively supported Workflow can also be configured with user-defined workflow and trackers
Nice svn pre-commit scripts
Hello all, 1. I need a script that stops commits that have empty log messages. Like this http://stackoverflow.com/questions/869248/windows-pre-commit-hook-for-comment-length-subversion Is there any script that run both under Linux and Windows (better: written in Python) 2. Please point me to some nice pre-commit hooks you know :) Thanks in advance, Nguyen Vu Hung
Re: Does svn export performs any kind of outbound connection
(2011/03/10 10:18), Andy Levy wrote: There is. For the command line, see usage #2 when you run svn help export. For Tortoise, see http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-export.html You got me :) I did google and reached that page. Howerver, I only "read" the screenshot and skipped everything esle. Thanks again. > As far as I tried, it seems that tortoiseSVN does not support exporting from > a local working svn folder. It does; see the link above. Be sure to read the whole page. If you stop at the screenshot, you'll miss the portion relevant to your question.
Re: Does svn export performs any kind of outbound connection
(2011/03/10 9:31), Andy Levy wrote: On Wed, Mar 9, 2011 at 21:26, Nguyen Vu Hung (VNC) wrote: Folks, Just a quick question: Does svn export performs any kind of outbound connection (like http) other than localhost? svn export only makes a connection between the client and the server, and only if you export using a URL (as opposed to doing an export from a working copy). Just like any other Subversion command that interacts with the server. So, svn export http://hostname/path/to/dir does make connections to svn servers. Does svn export path/to/working/dir makes connections to svn servers? Because I am working with a remote svn server that is quite big in size and the Internet connection is quite slow. What I want to do is: delete all .svn folder on a checked out repo. Under Windows, I can grep and delete all .svn folder but I don't know if there is any "smart" way to do that with the feature that svn and/or tortoiseSVN provides. As far as I tried, it seems that tortoiseSVN does not support exporting from a local working svn folder. Best regards, Nguyen Vu Hung
Does svn export performs any kind of outbound connection
Folks, Just a quick question: Does svn export performs any kind of outbound connection (like http) other than localhost? TIA, Nguyen Vu Hung
mod_dav_svn as a sub module of subversion
Hello all, Just curious, why mod_dav_svn is distributed as a sub module of svn instead of an idependent apache httpd module? BR, Nguyen Vu Hung Original Message Subject:Subversion 1.6.16 Released Date: Thu, 3 Mar 2011 14:02:59 -0600 From: Hyrum Wright To: announce , announce , Subversion Development , users http://subversion.apache.org/security/CVE-2011-0715-advisory.txt
Re: Using svn with cron?
(2011/03/07 12:49), bimininavels wrote: Where is svn's stderr? svn &> /some/file ?
Re: Subverion 1.7 Centralized Metadata Storage
(2011/02/22 17:18), Ulrich Eckhardt wrote: On Tuesday 22 February 2011, Nguyen Vu Hung (VNC) wrote: * This way makes svn git-like :), my first impression is that: subversion will be distributed, not centralized :) SVN has one .svn directory in every (versioned) child directory of a working copy. This has the effect that every child directory of a working copy is itself a working copy. SVN 1.7 wants to centralise this, i.e. only use a single place to store this. This is a handy replacement for svn export function. Backward compatibility with 1.6 is another big concern who wants to upgrade from 1.6 or maintaining an ecosystem of both 1.6 and 1.7
Subverion 1.7 Centralized Metadata Storage
Hello all, Could anyone please explain a little on the following feature? Specifically, my questions are * How it affects the current subversion (1.6) features and performance * This way makes svn git-like :), my first impression is that: subversion will be distributed, not centralized :) Centralized Metadata Storage A key feature of the changes introduced in Subversion 1.7 is the centralization of worky copy metadata storage into a single location. Instead of a .svn directory in every directory in the working copy, Subversion 1.7 working copies have just one .svn directory—in the root of the working copy. This directory includes (among other things) an SQLite-backed database which contains all of the metadata Subversion needs for that working copy. Even though the data is stored in a structured format, the relationships between the data are complex. We highly discourage external tools from modifying the data held in this database, as such modification is likely to result in working copy corruption.
