It does seem a bit strange that we all sell the value of fossil partly
because it has a wiki and ticket system built in. but then we don't eat
our own dog food.
I'm no better on my personal projects... but perhaps RSS can also play a
role here. Or if one could subscribe to the email updates
On 6/26/18, Richard Hipp wrote:
> it is mostly harmless.
In fact, the message comes from fossil_warning() Quite harmless.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On 6/26/18, Dan Barbarito wrote:
> Hello everybody,
>
> I figured I'd share a bug I found on here since tickets by anonymous
> users seem to be disabled. I am using the latest code in the trunk
> branch and I noticed that if you run "fossil checkout" on the same
> check-in twice in a row then you
Hello everybody,
I figured I'd share a bug I found on here since tickets by anonymous
users seem to be disabled. I am using the latest code in the trunk
branch and I noticed that if you run "fossil checkout" on the same
check-in twice in a row then you get an error that says "Missed call to
On 6/26/18, Chad Perrin wrote:
>
> I am running Fossil v2.5 here:
>
> $ fossil version
> This is fossil version 2.5 [188a0e2904] 2018-02-07 18:48:14 UTC
>
> I see no Markdown formatting option for tickets when visiting the web UI
> via `fossil serve`:
Go to /Admin/Tickets and edit the
On Tue, Jun 26, 2018 at 12:05:51PM -0400, Richard Hipp wrote:
> On 6/26/18, Andy Goth wrote:
> > Is there a reason why Fossil tickets don't allow markdown? The format
> > options are wiki, HTML, plain text, and [links only].
>
> Markdown as a formatting option can be added by configuration.
>
Le 26/06/2018 à 19:40, Richard Hipp a écrit :
On 6/26/18, sky5w...@gmail.com wrote:
But now I am confused by this thread?
If/When I add unversioned files, are their original paths stripped?
Are they stored differently than source code?
Unversioned files were created for the purpose of
On Tue, 26 Jun 2018 18:58:42 +0200, Andy Goth
wrote:
I think the next project that needs this feature should write a utility
script for themselves that uses the uv commands to extract files however
makes sense for them. This live experimentation is necessary to figure
what is needed in
Recently I had the pleasure of succeeding in enabling syntax
highlighting. Even
with that success I still found some things that could make the process
easier
and more robust.
One major issue would be that fossil by default inserts the following in
the
head:
This is fairly prohibitive
On 06/26/18 12:42, Richard Hipp wrote:
On 6/26/18, Andy Goth wrote:
A forum might be nice, but I don't want to have to enhance Fossil
just to be able to discuss enhancing Fossil!
Initial prototypes for the forum code are already in the tree. It
just needs some more work.
I noticed! Thank
On 6/26/18, Andy Goth wrote:
> A
> forum might be nice, but I don't want to have to enhance Fossil just to
> be able to discuss enhancing Fossil!
>
Initial prototypes for the forum code are already in the tree. It
just needs some more work. The recent email notification enhancements
were made
On 6/26/18, sky5w...@gmail.com wrote:
> But now I am confused by this thread?
> If/When I add unversioned files, are their original paths stripped?
> Are they stored differently than source code?
>
Unversioned files were created for the purpose of providing a place to
store build products when
On Mon, Jun 25, 2018 at 2:51 PM, Richard Hipp wrote:
> On 6/25/18, jungle Boogie wrote:
> > If I inadvertently forward my email along
> > to someone/group without modifying the footer, the person/group would
> > be able to alter my subscription.
>
> How can I fix that?
>
> --
> D. Richard Hipp
On 06/26/18 12:10, sky5w...@gmail.com wrote:
My repo's were built prior to the unversioned feature, so I have not
used this yet. And there is no benefit to migrating my candidate files
to unversioned since their history will remain in the repo without
complex shunning.
But now I am confused
My repo's were built prior to the unversioned feature, so I have not used
this yet. And there is no benefit to migrating my candidate files to
unversioned since their history will remain in the repo without complex
shunning.
But now I am confused by this thread?
If/When I add unversioned files,
Over the past several years I've been accumulating a long and growing
list of Fossil ideas, enhancement requests, and bug reports, and it's
not productive to keep them to myself, especially since it's been ages
since I've had enough free time to meaningfully contribute code. But
I've also not
I think the next project that needs this feature should write a utility
script for themselves that uses the uv commands to extract files however
makes sense for them. This live experimentation is necessary to figure
what is needed in practice. No one is forced to wait for any changes to
be
On Tue, 26 Jun 2018 18:33:22 +0200, Stephan Beal
wrote:
On Tue, Jun 26, 2018 at 5:45 PM wrote:
Can unversioned files respect their original paths when added?
I have several locations for bitmaps, icons, pdf's, etc.
They do not necessarily reside in an isolated folder.
yes, same here,
On 06/26/18 11:05, Richard Hipp wrote:
On 6/26/18, Andy Goth wrote:
Is there a reason why Fossil tickets don't allow markdown? The format
options are wiki, HTML, plain text, and [links only].
Markdown as a formatting option can be added by configuration.
I apologize, I was unclear. When
Hi,
On 2018-06-26 at 09:35 -0400
Richard Hipp wrote:
>Since Rafal's original inquiry, I have modified the email notification
>logic to use quoted-printable instead of base64. Quoted-printable is
>not as clean as plain-old 8bit, but it is much more readable than
>base64. Acceptable compromise?
On Tue, Jun 26, 2018 at 5:45 PM wrote:
> Can unversioned files respect their original paths when added?
> I have several locations for bitmaps, icons, pdf's, etc.
> They do not necessarily reside in an isolated folder.
>
That wouldn't work cross-platform. You might store file the C:\D\e\f.txt
On Tue, 26 Jun 2018 18:12:54 +0200, Richard Hipp wrote:
On 6/26/18, j. van den hoff wrote:
turning this setting on by default might also offer the "least
surprise" for the user
It isn't an on/off setting. I was not clear. The setting is the name
of the directory that is the root of the
On 6/26/18, j. van den hoff wrote:
> turning this setting on by default might also offer the "least
> surprise" for the user
It isn't an on/off setting. I was not clear. The setting is the name
of the directory that is the root of the unversioned file hierarchy.
An empty string for this
On Tue, 26 Jun 2018 17:31:32 +0200, Richard Hipp wrote:
My thought was to provide a new setting (perhaps versionable) that
specified a directory relative to the root of the check-out into which
unversioned files are written whenever one does "fossil update" or
"fossil checkout". If the
On 6/26/18, Andy Goth wrote:
> Is there a reason why Fossil tickets don't allow markdown? The format
> options are wiki, HTML, plain text, and [links only].
Markdown as a formatting option can be added by configuration.
Perhaps you are asking for Markdown support to be added to the default
Is there a reason why Fossil tickets don't allow markdown? The format
options are wiki, HTML, plain text, and [links only].
--
Andy Goth |
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
Can unversioned files respect their original paths when added?
I have several locations for bitmaps, icons, pdf's, etc.
They do not necessarily reside in an isolated folder.
Thanks for the new Fossil features!
On Tue, Jun 26, 2018 at 11:31 AM, Richard Hipp wrote:
> My thought was to provide
My thought was to provide a new setting (perhaps versionable) that
specified a directory relative to the root of the check-out into which
unversioned files are written whenever one does "fossil update" or
"fossil checkout". If the setting is missing or empty, then Fossil
works as it does now. If
On Tue, 26 Jun 2018 17:08:48 +0200, Richard Hipp wrote:
Unversioned files do not appear in the local check-out, by design. It
would be an enhancement to make them do so.
But you are not the first to request that capability. I've been on a
Fossil-enhancement binge lately - perhaps I can find
Unversioned files do not appear in the local check-out, by design. It
would be an enhancement to make them do so.
But you are not the first to request that capability. I've been on a
Fossil-enhancement binge lately - perhaps I can find the time to fix
that for you...
On 6/26/18, j. van den
On 06/21/2018 10:00 PM, E Cruz wrote:
On 06/21/2018 08:38 PM, Richard Hipp wrote:
Please rebuild your Fossil using the latest trunk check-in, then try
your clone using the new --nocompress option. Report back whether or
not this solves your problem.
Using the new option cuts the cloning time
today I convinced a colleague to give fossil a try. so we set up a project
(two checkouts/clones, one central server/repo), using a planned journal
article (to be written in latex) as the test case.
now, while I never have used 'unversioned files' so far, he immediately
wanted to try this
Since Rafal's original inquiry, I have modified the email notification
logic to use quoted-printable instead of base64. Quoted-printable is
not as clean as plain-old 8bit, but it is much more readable than
base64. Acceptable compromise?
On 6/26/18, Rafal Bisingier wrote:
> Hi
>
> Richard asked
Hi all:
In message <20180626110936.3524bd1f@puter>,
Rafal Bisingier writes:
>Richard asked me to post it on the list for discussion, so here it is:
>The new email notification functionality in fossil use base64 as
>Content-Transfer-Encoding. I personally prefer use of 8bit encoding,
>which have a
On 2018-06-22 20:40, Joerg Sonnenberger wrote:
[---]
> BTW, the main mercurial list uses the following mail format for "batch"
> changes:
>
> https://www.mercurial-scm.org/pipermail/mercurial-devel/2018-June/117551.html
This is highly machine parse-friendly. I like it a lot.
--
Kind
perfect, thanks a lot!
On Tue, 26 Jun 2018 13:22:40 +0200, Richard Hipp wrote:
The mv-rm-files setting used to require a compile-time option in order
to function. I have removed that requirement. mv-rm-files now works
without special compile-time options.
On 6/26/18, j. van den hoff
The mv-rm-files setting used to require a compile-time option in order
to function. I have removed that requirement. mv-rm-files now works
without special compile-time options.
On 6/26/18, j. van den hoff wrote:
> I have not fiddled with this for some time and now I do no longer recall
> how
I have not fiddled with this for some time and now I do no longer recall
how exactly this setting is managed. it is mentioned in several of the
help pages and I do have an entry
in my global `.fossil' database
INSERT INTO global_config VALUES('mv-rm-files','on');
(I do no longer recall when
Le 26/06/2018 à 09:25, j. van den hoff a écrit :
On Mon, 25 Jun 2018 23:57:35 +0200, jungle Boogie
wrote:
On 25 June 2018 at 14:51, Richard Hipp wrote:
On 6/25/18, jungle Boogie wrote:
If I inadvertently forward my email along
to someone/group without modifying the footer, the
On Mon, 25 Jun 2018 23:57:35 +0200, jungle Boogie
wrote:
On 25 June 2018 at 14:51, Richard Hipp wrote:
On 6/25/18, jungle Boogie wrote:
If I inadvertently forward my email along
to someone/group without modifying the footer, the person/group would
be able to alter my subscription.
How
40 matches
Mail list logo
