On Thu, Dec 13, 2012 at 11:37 AM, C. Thomas Stover <[email protected]>wrote:
> On Thu, 13 Dec 2012 09:27:03 -0700 > Matt Welland <[email protected]> wrote: > > > One partial solution available today is to use http://chiselapp.com. > > Simply use their "clone repo" feature with regular pull. > > What exactly does that do over a regular clone & pull? > Nothing really except that chiselapp will regularly pull from the parent. The point I was trying to make is that using chiselapp you can create public forks quite easily. What was missing was a mechanism to aggregate or document the forks so that people looking at a repo can find them. James Turner has indicated that he is interested in adding such a mechanism into chiselapp which I think will be great. I also think that such a feature would be very beneficial if integrated into fossil itself. If I use chiselapp or my own private server to clone the fossil-scm.comsite there is no record of the fork at the fossil-scm site. I personally think that having pointers to forks of the project would potentially stimulate more development activity. Certainly I'd like to have that for my own projects. Being able to pull in just a single branch from one of those forks would be icing on the cake. > -- > www.thomasstover.com > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
