Then what is the point of recvfrom? It will then just reduce to the repo where the artifact was created. This might be useful, but it is not what recvfrom means.
Op zo 17 dec. 2017 18:11 schreef Ron W <ronw.m...@gmail.com>: > On Sun, Dec 17, 2017 at 7:00 AM, < > fossil-users-requ...@lists.fossil-scm.org> wrote: >> >> Date: Sun, 17 Dec 2017 09:56:57 +0000 >> From: Mark Janssen <mpc.jans...@gmail.com> >> Subject: Re: [fossil-users] fossil-users Digest, Vol 119, Issue 28 >> Message-ID: >> <CADJpCb=AJUXV-zx6jZ6NJXB63MUZnNXPT4cQ5GUr= >> o5bgtr...@mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Unless I am misunderstanding what you mean by permanent record, I don't >> think this is possible in a DVCS. In a DVCS the remote can be different >> and >> even change between pull/syncs >> > > I was referring to the difference between "artifacts" and entries in a > table in the database. > > Fossil only sync's artifacts between repositories. Anything in the db that > isn't an artifact is local metadata. > > Besides tags added when a commit is made, Fossil allows additional tags to > be created. It does this by creating "control artifacts", therefore making > these additional tags sync-able between repos. > > By adding "rcvfrom" tags to commits received from the other repos, any > given commit would then be trace-able to its originating repo - even if any > of the intermediate repos is no longer available. > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
