Hi, On Wed, May 27, 2009 at 4:34 PM, Russel Winder <russel.win...@concertant.com> wrote: > Is it guaranteed that the Git read-only mirror repository will always be > exactly up to date to the Subversion repository? (i.e. will every commit > to the Subversion store cause a refresh of the Git read-only mirror?)
Yes. The mirror is listening for commit notification messages and will automatically update itself whenever it sees commons-cli commits. The delay is typically just a few seconds. > However if there is potential delay in mirroring or if a committer wants > to use Git to commit to the Subversion repository using Git then a clone > of the read-only mirror needs to be retargetted to the Subversion store > directly. That's also possible, though the instructions [1] are still a bit sketchy. With that setup it's even possible to commit directly to the Subversion repository from your Git clone! > It would be good if this page explained how to retarget the clone taken > so that it can be kept up to date with Subversion directly. i.e. What > is the sequence of instructions that allow "git svn fetch" to refresh > the git clone from the Subversion repository and "git svn dcommit" will > commit to the Subversion repository. As mentioned by others, we'd love to see suggestions (better yet, patches) of improvements on the infrastructure-dev@ mailing list or in the INFRA Jira under the Git component. [1] http://wiki.apache.org/general/GitAtApache BR, Jukka Zitting --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
