Re: [fossil-users] tangent vs. wyoung on recent commti

On Dec 18, 2017, at 8:22 PM, jungle boogie wrote: > > I can't remember the repo drh mentioned TH3, the paid-for test harness for SQLite: https://sqlite.org/th3.html > So if you committed something as drh with an improved overview section > showing gpg keys, would

Re: [fossil-users] tangent vs. wyoung on recent commti

Thus said Warren Young on Mon, 18 Dec 2017 17:55:16 -0700 I want to restrict this thread to the technical issues: preventing wyoung/tangent confusions, or helping Donny trust Alice, or or giving Donny the tools to *not* trust Alice just because Bob trusts Alice. I can't remember the repo drh

Re: [fossil-users] tangent vs. wyoung on recent commti

On Dec 18, 2017, at 5:55 PM, Warren Young wrote: > > Git does it by using email addresses for identity instead of user names It also occurs to me that Git typically inverts the push/pull relationship as compared to Fossil. I can’t get random checkins into Linus’ git tree

Re: [fossil-users] tangent vs. wyoung on recent commti

On Dec 17, 2017, at 1:44 PM, Kevin wrote: > > I believe deception and impersonation are important. I agree. One of the core tenets of Fossil is durable accountability, and here we have a case where it allows the who-did-what history to be muddied. What Fossil allowed in

Re: [fossil-users] tangent vs. wyoung on recent commti

Fwiw, i agree completely, plus suspect (without knowing for certain) that including a user's IP (and thus, indirectly, location) in the permanent record _might_ run afoul of privacy laws in some jurisdictions. - stephan Sent from a mobile device, possibly from bed. Please excuse brevity,

Re: [fossil-users] tangent vs. wyoung on recent commti

2017-12-18 5:58 GMT+01:00 Ron W: > All I'm suggesting is that the information already being put in the > "rcvfrom" table (that DRH mentioned) also be saved as tags to the commits > they refer to. Therefore, the tags will have the same meaning as the entries > in the existing "rcvfrom" table.

Re: [fossil-users] tangent vs. wyoung on recent commti

On Sun, Dec 17, 2017 at 9:11 PM, <fossil-users-requ...@lists.fossil-scm.org> wrote: > > Date: Sun, 17 Dec 2017 18:13:17 + > From: Mark Janssen <mpc.jans...@gmail.com> > Subject: Re: [fossil-users] tangent vs. wyoung on recent commti > > Then what is the point

Re: [fossil-users] tangent vs. wyoung on recent commti

On Fri, 15 Dec 2017 13:52:55 -0500, D. Richard Hipp wrote: >On 12/15/17, Andy Bradford wrote: >> Thus said Warren Young on Thu, 14 Dec 2017 12:13:18 -0700: >> >>> Fossil arguably  has a  bug here, where  if you check  a change  in as >>> local user name

Re: [fossil-users] tangent vs. wyoung on recent commti

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 : > On Sun, Dec 17, 2017 at 7:00 AM, < >

Re: [fossil-users] tangent vs. wyoung on recent commti

On Sun, Dec 17, 2017 at 7:00 AM, wrote: > > Date: Sun, 17 Dec 2017 09:56:57 + > From: Mark Janssen > Subject: Re: [fossil-users] fossil-users Digest, Vol 119, Issue 28 > Message-ID: >

Re: [fossil-users] tangent vs. wyoung on recent commti

On 12/15/17, Andy Bradford wrote: > Thus said Warren Young on Thu, 14 Dec 2017 12:13:18 -0700: > >> Fossil arguably has a bug here, where if you check a change in as >> local user name ``tangent'', as I do here, then *later* do a ``fossil >> sync'' to a URL with a

Re: [fossil-users] tangent vs. wyoung on recent commti

Thus said Warren Young on Thu, 14 Dec 2017 12:13:18 -0700: > Fossil arguably has a bug here, where if you check a change in as > local user name ``tangent'', as I do here, then *later* do a ``fossil > sync'' to a URL with a user name, some bit of the local on-disk state > remembers that

Re: [fossil-users] tangent vs. wyoung on recent commti

On Thu, Dec 14, 2017 at 9:38 PM, Ron W wrote: > Local, command line usage seems to grant the command line user full > permissions as long as the user has RW access to the repo file, itself. > > Right now, I can't test this to confirm this behavior. > That's correct: all CLI

Re: [fossil-users] tangent vs. wyoung on recent commti

On Thu, Dec 14, 2017 at 2:31 PM, <fossil-users-requ...@lists.fossil-scm.org> wrote: > > Date: Thu, 14 Dec 2017 12:31:21 -0700 > From: Scott Robison <sc...@casaderobison.com> > Subject: Re: [fossil-users] tangent vs. wyoung on recent commti > > I'd bet that you

Re: [fossil-users] tangent vs. wyoung on recent commti

I'd bet that you can commit as anyone and push it if you have that access. You probably wouldn't keep that access for long, though. On Dec 14, 2017 12:13 PM, "Warren Young" wrote: > On Dec 14, 2017, at 10:19 AM, jungle Boogie > wrote: > > > > So

Re: [fossil-users] tangent vs. wyoung on recent commti

On Dec 14, 2017, at 10:19 AM, jungle Boogie wrote: > > So Warren edited a file at the same exact time as tangent? Fossil arguably has a bug here, where if you check a change in as local user name “tangent”, as I do here, then *later* do a “fossil sync” to a URL with a

Re: [fossil-users] tangent vs. wyoung on recent commti

On 14 December 2017 at 10:07, Richard Hipp wrote: > On 12/14/17, jungle Boogie wrote: >> Hi All, >> >> This commit caught my eye: >> http://fossil-scm.org/index.html/info/ec059849f5c73a43 >> >> User & Date:wyoung on 2017-12-13 21:37:20 >> Original User &

Re: [fossil-users] tangent vs. wyoung on recent commti

On 12/14/17, jungle Boogie wrote: > Hi All, > > This commit caught my eye: > http://fossil-scm.org/index.html/info/ec059849f5c73a43 > > User & Date:wyoung on 2017-12-13 21:37:20 > Original User & Date:tangent on 2017-12-13 21:37:20 > > So Warren edited a file at the same

[fossil-users] tangent vs. wyoung on recent commti

Hi All, This commit caught my eye: http://fossil-scm.org/index.html/info/ec059849f5c73a43 User & Date:wyoung on 2017-12-13 21:37:20 Original User & Date:tangent on 2017-12-13 21:37:20 So Warren edited a file at the same exact time as tangent? Clicking on tangent, I see this: