{"thread":{"id":"22457","subject":"git-svn and subversion revprops","startedAt":"2010-01-31T11:39:03Z","lastAt":"2010-02-02T09:38:48Z","messageCount":2,"participants":["Eli Barzilay","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"133180","messageId":"19301.27607.993690.703245@winooski.ccs.neu.edu","threadId":"22457","inReplyTo":null,"subject":"git-svn and subversion revprops","fromName":"Eli Barzilay","fromEmail":"eli@barzilay.org","sentAt":"2010-01-31T11:39:03Z","receivedAt":"2010-01-31T11:39:03Z","isPatch":false,"sender":{"key":"eli@barzilay.org","avatar":"https://avatars.githubusercontent.com/u/185905?v=4"},"body":"[This is possible an RTFM -- but as much as I've been digging around,\nI couldn't find anything about it.]\n\nI'm trying to play with git-svn in a project that uses subversion, and\nthere's one feature that I'd like to have -- make git-svn specify some\nrevision properties (eg, the `--with-revprop' to `svn commit') that\nwill identify it as coming from git-svn.\n\nThe thing is that we have a continuous build server that runs a\ncomplete build (and runs all tests) for every revision -- and I'm\ntrying to figure out a way to make it skip intermediate commits that\ncome from a git-svn.  The simplest way to do that would be a way to\nmark all git-svn revisions somehow, and I can later unmark the last\none in the chain so only that one will get built and tested.  It would\nbe even more convenient if I have a way to control the revprops on the\nlast commit separately, so there's no additional step involved.\n\nThe only other alternative that I see is some wrapper around git-svn\nthat connects to some script that will run on the server before and\nafter dcommitting changes, and that script will do the necessary work.\nIs there a way to specify hook scripts to run around a dcommit?\n\nActually, such hooks can also be used to lock the svn reposity while\ngit-svn is working -- I couldn't figure out what happens when there's\nsome commit that comes in while git-svn is running.  My guess is\nthat it'll either get stuck and throw an error, or maybe try to\ncontinue if possible.  Such hooks could make that part more robust, as\nwell as guarantee that each batch of svn-git commits are always\ntogether.\n\n-- \n          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:\n                    http://barzilay.org/                   Maze is Life!\n"},{"id":"133342","messageId":"20100202093848.GB28437@dcvr.yhbt.net","threadId":"22457","inReplyTo":"19301.27607.993690.703245@winooski.ccs.neu.edu","subject":"Re: git-svn and subversion revprops","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2010-02-02T09:38:48Z","receivedAt":"2010-02-02T09:38:48Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"Eli Barzilay <eli@barzilay.org> wrote:\n> [This is possible an RTFM -- but as much as I've been digging around,\n> I couldn't find anything about it.]\n> \n> I'm trying to play with git-svn in a project that uses subversion, and\n> there's one feature that I'd like to have -- make git-svn specify some\n> revision properties (eg, the `--with-revprop' to `svn commit') that\n> will identify it as coming from git-svn.\n\nHi, there's currently no way to commit revprops to svn with git svn.\n\n> The thing is that we have a continuous build server that runs a\n> complete build (and runs all tests) for every revision -- and I'm\n> trying to figure out a way to make it skip intermediate commits that\n> come from a git-svn.  The simplest way to do that would be a way to\n> mark all git-svn revisions somehow, and I can later unmark the last\n> one in the chain so only that one will get built and tested.  It would\n> be even more convenient if I have a way to control the revprops on the\n> last commit separately, so there's no additional step involved.\n> \n> The only other alternative that I see is some wrapper around git-svn\n> that connects to some script that will run on the server before and\n> after dcommitting changes, and that script will do the necessary work.\n> Is there a way to specify hook scripts to run around a dcommit?\n\nNo, there are no hooks currently run directly by git svn.  dcommit uses\ngit-rebase internally, so git-rebase can run the pre-rebase hook (never\ntried it myself, though).\n\n> Actually, such hooks can also be used to lock the svn reposity while\n> git-svn is working -- I couldn't figure out what happens when there's\n> some commit that comes in while git-svn is running.  My guess is\n> that it'll either get stuck and throw an error, or maybe try to\n> continue if possible.  Such hooks could make that part more robust, as\n> well as guarantee that each batch of svn-git commits are always\n> together.\n\nCould be useful in some cases.  I've never actually seen any project use\nSVN locks, though, and had completely forgotten about them until now...\n\n-- \nEric Wong\n"}]}