On Sun, Oct 16, 2011 at 5:57 AM, Stephan Beal <[email protected]> wrote:
> Hi, all, > > i've found myself in a situation where a user would like to commit some > changes to the json branch but doesn't have commit access. What i'd like to > do is set up a clone on my system, give him commit access to that, and then > i would act as the gateway to pipe the changes back into the main > repo (i.e. be the "lieutenant" in Linux jargon). > I'll need a copyright release<http://www.fossil-scm.org/fossil/doc/trunk/www/copyright-release.html>from that user in either case. And once I get the copyright release, then he or she can have direct commit access. > > i've never needed such a thing in fossil, and i'm not sure how i should (or > should not!) go about it, but i'm guessing at least a few of you have such a > constellation. Have and of you got any tips on how (in terms of workflow) i > should/should not go about this? Is this even doable with fossil's > model (without any git export/import voodoo or whatnot)? > > -- > ----- stephan beal > http://wanderinghorse.net/home/stephan/ > > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
