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
Op za 16 dec. 2017 21:42 schreef Ron W <ronw.m...@gmail.com>: > On Sat, Dec 16, 2017 at 7:00 AM, < > fossil-users-requ...@lists.fossil-scm.org> wrote: > >> Date: Fri, 15 Dec 2017 13:52:55 -0500 >> From: Richard Hipp <d...@sqlite.org> >> Subject: Re: [fossil-users] tangent vs. wyoung on recent commti >> >> On 12/15/17, Andy Bradford <amb-fos...@bradfords.org> wrote: >> > As stated in the past, Fossil is meant for a tighter group of >> > developers---perhaps this perception has changed---one in which >> > impersonation is unlikely. >> > >> >> I was very aware of all of these factors when I designed Fossil, 10 >> years ago. Impersonation was a concern. But in a DVCS, there really >> is no way around it. >> >> Defenses include: >> >> (1) The rcvfrom table that shows clearly where all artifacts >> originated, thus allowing the originator of a deception to be tracked >> down and dealt with administratively. >> > > Maybe there should be a way to store this rcvfrom table in artifacts so > the data is part of the permanent Fossil record. > > Maybe as control artifacts to auto-tag each each commit received via > sync/pull/push? > > _______________________________________________ > 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
