Haha, yeah that is one of the many in my fossil cheat sheet. ;)
I'm still on the hook to deliver that. Just need to sanitize and prettify.
Right now it is combined with my Windows Batch/Doskey commands.
I was hoping to replace all that with the fossil api.
On Tue, Oct 15, 2013 at 3:05 PM, j. van
On Tue, Oct 15, 2013 at 1:09 PM, j. van den hoff
wrote:
> I'm in the process of giving the ticket system a try for a collaboration
> where we need to keep track of text document changes on the one side and
> have a facility to report problems/issues observed with the system
> (hardware, not softwa
thanks to you and Lluís and sorry for the noise (asking without checking
first ...)
On Tue, 15 Oct 2013 22:11:03 +0200, Stephan Beal
wrote:
IIRC you can change all of them in the admin/setup pages.
(sent from a mobile device - please excuse brevity, typos, and
top-posting)
- steph
IIRC you can change all of them in the admin/setup pages.
(sent from a mobile device - please excuse brevity, typos, and top-posting)
- stephan beal
http://wanderinghorse.net
On Oct 15, 2013 10:09 PM, "j. van den hoff"
wrote:
> I'm in the process of giving the ticket system a try for a colla
On Tue, Oct 15, 2013 at 10:09:41PM +0200, j. van den hoff wrote:
> I'm in the process of giving the ticket system a try for a
> collaboration where we need to keep track of text document changes
> on the one side and have a facility to report problems/issues
> observed with the system (hardware, no
I'm in the process of giving the ticket system a try for a collaboration
where we need to keep track of text document changes on the one side and
have a facility to report problems/issues observed with the system
(hardware, not software, ...).
question: the ticket type is predefined to be o
On Tue, 15 Oct 2013 19:39:00 +0200, wrote:
I got something similar when I inadvertently left the prefix character
'#'
in front of my comment.
thanks a lot! would never have thought of that but apparently (if I've
understood his answer correctly) he did just that on purpose, presuming
th
I got something similar when I inadvertently left the prefix character '#'
in front of my comment.
On Tue, Oct 15, 2013 at 1:23 PM, j. van den hoff
wrote:
> I'm asking this for a colleague just starting to use fossil under windows
> (with which I have no experience whatsoever):
>
> he succeeded
I'm asking this for a colleague just starting to use fossil under windows
(with which I have no experience whatsoever):
he succeeded to clone the repo (after circumventing the previously
mentioned SSL cerificate problem) and to open it.
so he added some new file to the checkout dir and did
On Tue, Oct 15, 2013 at 7:07 PM, j. van den hoff
wrote:
> "server does not respond" as the error message. if that message comes from
> fossil to (I presume it does, it might be a
>
it would surprise me - that's not correct English.
[stephan@host:~/cvs/fossil/fossil/src]$ grep 'server does not re
On Tue, 15 Oct 2013 18:53:24 +0200, Ron Wilson wrote:
You saidd Fossil was server via CGI? In that case, the webserver is
handling the SSL negotiation. Also, as best I know, Fossil does not
handle
the server side of SSL, anyway. See:
http://fossil-scm.org/index.html/doc/tip/www/ssl.wiki
htt
On Tue, 15 Oct 2013 19:04:59 +0200, Stephan Beal
wrote:
On Tue, Oct 15, 2013 at 7:03 PM, j. van den hoff
wrote:
is there a way to track this down? let me know if I can be of any help.
i know zero about SSL (other than what the acronym means), so i won't be
yes, that's about equals my o
On Tue, Oct 15, 2013 at 7:03 PM, j. van den hoff
wrote:
> is there a way to track this down? let me know if I can be of any help.
>
i know zero about SSL (other than what the acronym means), so i won't be
any help here unless it involves only a quick grep.
--
- stephan beal
http://wandering
On Tue, 15 Oct 2013 18:59:41 +0200, Stephan Beal
wrote:
On Tue, Oct 15, 2013 at 6:39 PM, j. van den hoff
wrote:
question: my understanding is these warnings and the prompting for how
to
proceed is done by fossil, right? if so, am I do understand that this
is a
fossil problem? should I e
On Tue, Oct 15, 2013 at 6:39 PM, j. van den hoff
wrote:
> question: my understanding is these warnings and the prompting for how to
> proceed is done by fossil, right? if so, am I do understand that this is a
> fossil problem? should I expect
> the "server did not reply" message after answering "y
You saidd Fossil was server via CGI? In that case, the webserver is
handling the SSL negotiation. Also, as best I know, Fossil does not handle
the server side of SSL, anyway. See:
http://fossil-scm.org/index.html/doc/tip/www/ssl.wiki
http://fossil-scm.org/index.html/doc/tip/www/server.wiki
On Tu
hi,
a colleague in the US just tried to clone a cgi-served repo via https
(residing in germany) like
fossil clone https:usrname@server/repos/somerepo
and received (contrary to myself) warning messages regarding
"SSL verification failed: self signed certificate in certificate chain"
etc.
as o
On Tue, Oct 15, 2013 at 11:19 AM, Gour wrote:
> On Tue, 15 Oct 2013 10:05:07 -0400
> Ron Wilson wrote:
>
> > 2 questions:
> >
> > 1. Do you need to track all the commits from the upstream side?
> >
> > 2. Do you need to push all of your commits?
> >
> > If either one is yes, you could do it, but
I have done what Ron suggests before and it works well but it is initially
complicated to set up. A generic script or tool to do this would be very
nice to have available.
I created "vendor branches", one for each system, the git branch in fossil
would track the git master and the fossil branch in
On Tue, 15 Oct 2013 15:08:57 +0200
Stephan Beal wrote:
> Nope. It would not be wrong to label Fossil as "100% organic" in
> nature ;).
:-)
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailma
On Tue, 15 Oct 2013 10:05:07 -0400
Ron Wilson wrote:
> 2 questions:
>
> 1. Do you need to track all the commits from the upstream side?
>
> 2. Do you need to push all of your commits?
>
> If either one is yes, you could do it, but will be a lot of work. If
> both are yes, probably best to just
2 questions:
1. Do you need to track all the commits from the upstream side?
2. Do you need to push all of your commits?
If either one is yes, you could do it, but will be a lot of work. If both
are yes, probably best to just use git.
Otherwise, you can have 2 "transfer work areas" that are bot
On Tue, Oct 15, 2013 at 1:44 PM, Gour wrote:
> Is there some roadmap for Fossil available providing some list of the
> features which might end up being implemented (soon)?
>
Nope. It would not be wrong to label Fossil as "100% organic" in nature ;).
--
- stephan beal
http://wanderinghorse
Is there some roadmap for Fossil available providing some list of the
features which might end up being implemented (soon)?
Sincerely,
Gour
--
Even a man of knowledge acts according to his own nature, for
everyone follows the nature he has acquired from the three modes.
What can repression ac
Hello,
I'm very happy with Fossil for internal or private use, but considering
that Git is all around, I wonder if there is some safe recipe for
incremental updates and/or 2-way sync between Fossil & Git for, at
least, specific Git branch?
Sincerely,
Gour
--
One must deliver himself with the
25 matches
Mail list logo
