Manuzhai wrote: >>That leaves a good margin for someone who'd like to go for the bounty ;) > > > I'm certainly tempted to get into it, but obviously I can't commit it. > I'm not sure what exactly the demands for the bounty would be, or how > high the bounty is.
I'm not sure of these details either, just wanted to open the concept for discussion. In terms of the demands or acceptance criteria, I think that any solution should be at least to a standard where the maintainers are happy to commit it. The whole concept of what history and changelogs mean for subset repos when they originate outside the subset, probably needs a bit of thought. Should it be opaque? If the subsets are being used to prevent access to different areas in the repo (possibly in concert with fine-grained repo access rights via apache), then any solution should be able to support and respect that. My feeling is that as long as trac enforces browsing to the subset, anything else that svn might return in the logs should still be fair game - a user with command-line svn client will still be able to see that stuff. Thoughts? John _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
