#994: Fix SVN properties for git-svn users
--------------------+-------------------------------------------------------
Reporter: Util | Owner: Util
Type: todo | Status: assigned
Priority: normal | Milestone:
Component: none | Version: 1.5.0
Severity: medium | Keywords: git svn git-svn property properties
auto-prop
Lang: | Patch:
Platform: all |
--------------------+-------------------------------------------------------
Changes (by Util):
* status: new => assigned
Comment:
This problem was identified and discussed in the 2009-09-01 #parrotsketch
IRC meeting [http://irclog.perlgeek.de/parrotsketch/2009-09-01#i_1454166]:
{{{
18:55 chromatic mikehh, question?
18:56 mikehh I am getting a lot of codetest/distro_tests failures
with svn properties from git svn users
18:56 mikehh any way to sort this out?
18:57 chromatic We talked about autoprops set on the server with a
commit hook.
18:57 allison are they not able to set svn props?
18:57 * japhb fights the urge to troll an old argument
18:58 allison they coul
18:58 chromatic The old argument "Why are these properties useful
again?"
18:58 japhb allison, that's correct, git-svn does not handle svn
props. So git-svn users need to have a normal svn checkout, and remember
to run the codetests in there after committing new files.
18:59 japhb *have a normal svn checkout *also*
18:59 allison (cellphone keyboard)
18:59 allison that doesn't sound so terrible
19:00 japhb allison, no, but very easy to forget. :-/
19:00 mikehh well the svn:keywords appear in the header
19:00 mikehh of the file that is
19:01 allison chromatic: server-side hooks are a good idea, but how do
we know for sure when to apply them?
19:01 chromatic We *always* apply them.
19:01 japhb mikehh, I mean, easy for a git-svn user to forget to
give the svn props a hug, after doing a big commit people tend to think
they are done and go grab a beer.
19:01 chromatic They're basically the *same* on *every* file in the
repository.
19:01 allison c: not all props apply to all files
19:02 chromatic I can think of two files out of our 6500+ which have
different properties.
19:02 mikehh svn:mime_type for tests
19:02 allison txt vs binary, etc
19:02 Coke we wouldn't need the mime type if we had sane server
defaults.
19:02 japhb allison, but if there is a computer-understandable rule
that works 95% of the time, we should have the computer apply it, and let
humans override it.
19:02 duk3leto allison: there is no git svn propset
19:03 allison japhb: git users wouldn't be able to interact withit
19:04 allison but can correct later
19:04 duk3leto japhb: git svn propget works, just not setting
19:04 japhb duk3leto, nodnod
19:04 chromatic Let's move this discussion over to #parrot.
19:04 allison any volunteers
19:05 chromatic Volunteers for server-side hooks?
19:06 allison (can't join #parrot from here, but log my thumbs up for
exploring adding server-side hooks)
19:06 Util I wrote code months ago to analyse our SVN properties,
but just used it for manual corrections. Have not done serverside hooks,
but willing to try.
}}}
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/994#comment:1>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets