Hi fellow fossil users,
I'm sorry for such too long an email. Let me give you a short index
of it, so you could skip the rest if you are not interested in what
I'd like to talk about:
* description of my work processes
* small-scale
* large-scale
* suggestions on what could be improved to
(Fri, 21 Oct 12:14) Warren Young:
> https://www.fossil-scm.org/index.html/doc/trunk/www/checkin_names.wiki
just found a typo:
Index: www/checkin_names.wiki
==
--- www/checkin_names.wiki
+++ www/checkin_names.wiki
@@ -158,11
Thus said Nikita Borodikhin on Fri, 21 Oct 2016 16:02:33 -:
> == change sets - preparing the change ==
>
> I often end up having several sets of unrelated changes. For example,
> one set is my temporary change to the build system to disable some
> things to make build process
On Oct 21, 2016, at 10:02 AM, Nikita Borodikhin wrote:
>
> == color support - review the change, history analysis ==
>
> One should not underestimate the significance of color on terminals these
> days, that's why both git and mercurial and a lot of tools have color support
Hi,
However, xinetd or inetd are not recommended...
Best Regards
K.
De : Nathaniel Reindl
À : fossil-users@lists.fossil-scm.org
Envoyé le : Vendredi 21 octobre 2016 21h48
Objet : Re: [fossil-users] Can fossil bind to a single address?
On Fri, Oct 21, 2016, at
Hello,
Using fossil with xinetd using the following settings, browsing
repositories via the web interface does not work properly. My xinetd is
the one from Debian jessie.
service fossilmpa
{
type = UNLISTED
bind = 208.77.100.8
port = 8080
socket_type = stream
protocol = tcp
flags = NODELAY
On Fri, Oct 21, 2016, at 05:28 PM, Steven Gawroriski wrote:
> Is Fossil able to bind to a single IP address? There is `--localhost`
It doesn't seem that way, no. I've personally worked around it by employing
tcpsvd from Gerrit Pape's excellent ipsvd package. The inetd super server (and
its
Hello,
Is Fossil able to bind to a single IP address? There is `--localhost`
but that binds to 127.0.0.1 and `--port` for the port. However I would
like to listen on specific addresses, such as say 127.0.4.2 or a
specific public address. Right now to do this I have to host a server
with
Hi again,
Most of the time I try not to interact with people discuss.
However, I was astonished by what a community manager answered to another guy.
So I decided to give my opinion about it.
> « You admitted to not using branches, apparently because you don’t see the
> point of them in a
On Oct 21, 2016, at 18:55, K. Fossil user
wrote:
> However, xinetd or inetd are not recommended...
That ellipsis really should be filled in with more details. Would you perhaps
be willing to elaborate a bit on what you mean? —n
Wait, what's wrong with inetd?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
The thing is I have to have both changes locally in order to fix the
problem, but I do not want to commit some of them. Let me give you an
example.
Let's imagine I work on some embedded project. I have a device my project
is targetted to, and I have a development board based on a slightly
On Oct 21, 2016, at 5:57 PM, K. Fossil user
wrote:
>
> However, I was astonished by what a community manager answered to another guy.
You say that like you think I hold some kind of official title. I’m just
another Fossil user, like you. When I used that
I just had to share this blog post, which I found last night:
http://blog.endpoint.com/2014/05/git-checkout-at-specific-date.html
Yes, the Git alternative to “fossil up 2016-08-01” is
$ git checkout `git rev-list -n 1 --before=2016-08-01 master`
…and it takes a long blog post to
Greetings,
Due to some ill-conceived advice and over-enthusiastic scripting, I
managed to execute a command like this:
fossil ticket set e9d34a2552 +icomment "ivenkat added on
2016-10-21.18:50:20 PDT:
script checked in to [1a8ae0e34f]"
This failed with
SQLITE_ERROR: table ticketchng has no
Hi Warren,
On 10/21/2016 07:21 PM, Warren Young wrote:
On Oct 21, 2016, at 7:31 PM, Nikita Borodikhin wrote:
I would like to be able to commit only needed changes:
So say:
$ fossil ci Makefile state_machine.c
It’s actually less typing than defining a changelist and
On Oct 21, 2016, at 10:22 PM, Venkat Iyer wrote:
>
> Due to some ill-conceived advice and over-enthusiastic scripting
Do you have some TH1 scripts (hooks, etc) installed? If so, can you share them?
> fossil ticket set e9d34a2552 +icomment "ivenkat added on
Hi Warren,
Thanks for the reply. No TH1 scripts, no hooks. The only customization
is adding "assigned_to" in the ticket through the GUI.
The icomment stuff must have recently changed. "User Comments" is
different than "comments". I used to do +comments and that used to append
to the end
On Oct 21, 2016, at 10:39 PM, Venkat Iyer wrote:
>
> Thanks for the reply. No TH1 scripts, no hooks. The only customization is
> adding "assigned_to" in the ticket through the GUI.
Actually, I can replicate this with a clean repo:
mkdir x
cd x
f new
Hi Andy,
On 10/21/2016 12:53 PM, Andy Bradford wrote:
Thus said Nikita Borodikhin on Fri, 21 Oct 2016 16:02:33 -:
== change sets - preparing the change ==
I often end up having several sets of unrelated changes. For example,
one set is my temporary change to the build system to
20 matches
Mail list logo