Ahh - so any easy kludge around this would be to create a single
directory thread parallel to your repositories and make use of the
WebDAV functionality (assuming you are using Apache as your host). Then
anyone with permissions can add a patch.
OR -
You create a patch file and attach it to your issue tracking system (we
never make code changes without an open code/issue request) as an
attachment. The issue tracking system will automagically notify all
interested parties to implement and test the patch. The patch is both
shared and stored. And if anyone makes changes to it, they can
modify/remove the existing patch.
Maybe I am getting to far into the workarounds, but in reading the
other thread currently floating, Team Server allows for both bug/issue
tracking/discussion as well as some semblance of version management. So
it seems to me that not all of the features in TS can realistically be
put into Subversion, anyway.
Regards,
Frank
John wrote:
>Nathan Kidd <nathan-svn <at> spicycrypto.ca> writes:
>
>
>
>>Why "without branching"? That's really just another way of saving your
>>work to a different location, like TS shelving. You've probably read
>>http://mikemason.ca/2005/03/30/
>>
>>
>
>Hi Nathan,
>
>Yep I did read that one. I want to avoid branching because shelving seems to be
>a way to share and review code patches that might not be good enough to commit.
>In just the same way patch files fly around on the dev list. (I don't think this
>is just about write-access, or lack of. It's also to do with peer-review).
>
>You write code, get your collegues to review the patch, if all is well, commit.
>All this you can do with (T)SVN, I'm just thinking about ways to facilitate the
>sharing and storing of patches.
>
>John
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
>
Received on Tue Aug 2 22:36:11 2005