On Sun, Dec 17, 2017 at 8:40 PM bch wrote:
> I'm using recent fossil:
> kamloops$ fossil version
> This is fossil version 2.5 [5419e7fcec] 2017-12-15 18:27:08 UTC
>
>
> trying to view annotate/blame for a file, and on Firefox (Build
> identifier: Mozilla/5.0 (X11; NetBSD amd64; rv:57.0) Gecko/201
On Sun, Dec 17, 2017 at 9:11 PM,
wrote:
>
> Date: Sun, 17 Dec 2017 18:13:17 +
> From: Mark Janssen
> Subject: 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 use
I'm using recent fossil:
kamloops$ fossil version
This is fossil version 2.5 [5419e7fcec] 2017-12-15 18:27:08 UTC
trying to view annotate/blame for a file, and on Firefox (Build
identifier: Mozilla/5.0 (X11; NetBSD amd64; rv:57.0) Gecko/20100101
Firefox/57.0) I get this:
The connection was rese
You can now see the canonical Fossil self-hosting repository using any
of the built-in skins by visiting links from this page:
https://www.fossil-scm.org/skins/
I have fixed a few of the more egregious problems in these built-ins
that have resulted from the recent Modern View timeline and other
en
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 ``tangent'', as I do here, then *later* do
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, <
> fossil-users-requ...@lists.fossil-scm.org> wrote:
>>
>>
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:
> bgtr...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Unless I am misunderstanding
The following command fails:
$ fossil tag add -n --user-override username tagname checkin
But this one works as expected:
$ fossil tag add --dryrun --user-override username tagname checkin
That's because -n is the short form for both --limit and --dryrun:
http://fossil-scm.org/index.html/artif
On 16 December 2017 at 20:33, Andy Bradford
wrote:
> Thus said David Mason on Sat, 16 Dec 2017 15:36:51 -0500:
>
> > I tried to add a tag to my fossil. After looking at the documentation
> > which said:
>
> The ``fossil tag'' command is for very low-level tag operations. You
> probably don't
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 :
> On Sat, Dec 16, 2017 at 7:00 AM, <
> fossil-users-requ...@lists.fossil-scm.
10 matches
Mail list logo