On 6/15/18, Ron W <ronw.m...@gmail.com> wrote: > On Fri, Jun 15, 2018 at 2:58 PM, > <fossil-users-requ...@lists.fossil-scm.org> > wrote: > >> >> Date: Fri, 15 Jun 2018 13:35:13 -0400 >> From: Richard Hipp <d...@sqlite.org> >> Subject: Re: [fossil-users] Perception of Fossil >> >> An alternative design sketch: >> >> (4) The pullrequest command creates a "bundle" out of the "anon-patch" >> branch and then transmits that bundle back to the server from which >> the clone originated. >> >> (5) The server accepts the bundle and parks it in a separate holding >> table, but does not merge it or otherwise make it available to average >> passers by. The server then sends email notifications to developers >> with appropriate privileges to let them know that a pull request has >> arrived. >> > > How does the bundle get transmitted to the server? If via a push, making > the bundle seems like extra work..
The user types "fossil pullrequest" and the changes get sent up to the server. Why does it matter what steps Fossil undertakes behind the scenes to make this happen? -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
