Hi,
I'm trying to access my personal repo server running at home. I'm doing it
from the office, behind a load balancer. If I login, I loose access after a
while (asks me to login again). The only solution I've found is to set the
"IP address terms used in login cookie" to 0, but is something I don
Ohhh, it's ok if you say so... I was worried about security issues, but I
didn't stop to think about them. I'll set it to 0 then.
Thanks!
On Mon, Mar 17, 2014 at 3:00 PM, Richard Hipp wrote:
>
>
>
> On Mon, Mar 17, 2014 at 3:27 PM, Abilio Marques
> wrote:
>
Just a random thought. For a few months I've been toying with the idea of
creating a "version control" plugin for Qt Creator. It got Bazaar,
ClearCase, GIT, Gerrit, Mercurial, SVN, and CVS... all of them except my
favorite one... Fossil. As I'm fond of fossil, I believe people should get
more Fossi
Hi,
I want to enable everyone access to the /doc files. I'm using my raspberry
pi to host my repos, one of them being my resumé (done with latex), and I
want everyone to be able to access to the latest version (of the PDF).
I have 2 questions:
1. Can I limit access just to PDF files. Actually, i
Apr 7, 2014 at 10:22 AM, Richard Hipp wrote:
>
>
>
> On Mon, Apr 7, 2014 at 10:47 AM, Abilio Marques
> wrote:
>
>> Hi,
>>
>> I want to enable everyone access to the /doc files. I'm using my
>> raspberry pi to host my repos, one of them being my re
But checkout capabilities are too high for that purpose, am I wrong? Any
other solutions?
On Mon, Apr 7, 2014 at 11:15 AM, Martin Gagnon wrote:
> On Mon, Apr 07, 2014 at 05:20:39PM +0200, Stephan Beal wrote:
> > On Mon, Apr 7, 2014 at 5:10 PM, Richard Hipp wrote:
> >
> > Unless... Maybe i
But Richard said turn them all off...
On Apr 7, 2014 10:22 AM, "Richard Hipp" wrote:
>
>
>
> On Mon, Apr 7, 2014 at 10:47 AM, Abilio Marques
> wrote:
>
>> Hi,
>>
>> I want to enable everyone access to the /doc files. I'm using my
>> r
Hi,
This doubt has been with me for a long time, but then I kinda forgot about
the deal.
Anyway, the thing is related to the comment text introduced during the
check-in. I want the web interface to show only the first line (in the case
of a multiline) over the timeline, but then when I click on a
Hi,
It's me, again with an doc URL question. This time I've realized that if I
put a branch name on it, it will serve the files on it. For example, if I
have a branch called "en", then the following will be valid:
/resume/doc/en/abiliojr.pdf
But if I tag an specific checkin with a tag, let's say
My mistake, I had filters added at: admin/access/Public pages
Sorry
On Sat, Apr 19, 2014 at 7:05 PM, Stephan Beal wrote:
> On Sun, Apr 20, 2014 at 1:28 AM, Abilio Marques
> wrote:
>
>> /resume/doc/en/abiliojr.pdf
>>
>> But if I tag an specific checkin with a tag
Hi,
Nowadays tools like Jenkins can run tests on triggers (or hooks), and it
works wonderful. But Jenkins is overkilling (Java based :s) to be a match
to the tiny but powerful and agile fossil. Even when this fellow ronperrela
did a nice job integrating Jenkins:
http://ronperrella.blogspot.com/20
I see there is a way to run a TH1 script. But as far as I see the th1
documentation, I can't find a way to invoke a shell script out of it. Any
ideas???
2014-05-27 8:04 GMT-04:30 Abilio Marques :
> Hi,
>
> Nowadays tools like Jenkins can run tests on triggers (or hooks),
Hi,
Let's say I want to do this setup:
Clone sqlite repo on a local server
Then clone the server into several machines, with the users pushing changes
Then, someday, I will want to update my sqlite "base" code.
In git, one would first fork the code from another repo, add a second
remote:
git rem
trying to run this from command line:
fossil test-th-eval 'http "http://localhost:8085/test?a=1";
fossil test-th-eval 'http "http://localhost:8085/test";
fossil test-th-eval 'http "http://localhost:8085/";
fossil test-th-eval 'http "http://www.google.com";
While on the other side I keep a nc -klv
he security measure, I will test it ASAP
2014-06-12 7:06 GMT-04:30 Jan Nijtmans :
> 2014-06-12 13:32 GMT+02:00 Abilio Marques :
> > trying to run this from command line:
> >
> > fossil test-th-eval 'http "http://localhost:8085/test?a=1";
> > fossil te
About the regexp setting, tried:
set th1-uri-regexp ".*"
http -asynchronous http://localhost:8085
With and without quote marks, didn't work. I ran it from the command line,
and it still says: url not allowed... hints?
2014-06-12 8:12 GMT-04:30 Abilio Marques :
> While
Ran it like this:
fossil test-th-eval "set th1-uri-regexp \.\* ; http https://localhost:8085";
still nothing...
2014-06-12 8:45 GMT-04:30 Jan Nijtmans :
> 2014-06-12 14:56 GMT+02:00 Abilio Marques :
> > About the regexp setting, tried:
> >
> > set th1-uri-reg
4.3.18 here, not working. FreeBSD 10.0
2014-06-19 13:06 GMT-04:30 Stephan Beal :
> On Thu, Jun 19, 2014 at 7:14 PM, Ron Wilson wrote:
>
>> Which shell? bash gives me the error: !: event not found
>>
>
> That's my historical experience with '!' as well, but it works here:
>
> [odroid@host:~/fo
Hi,
This is a stupid question, I've seen it asked several times, but I'm trying
my own version of the question here:
Cloning over ssh seems to be impossible if the user nobody doesn't have
cloning permissions. For me it seems ok, as cloning over ssh still requires
username and password or a valid
g?
2014-08-16 5:08 GMT-04:30 Stephan Beal :
> On Fri, Aug 15, 2014 at 3:14 PM, Abilio Marques
> wrote:
>
>> The extra mile question is: is there any security risk involved with
>> giving 'nobody' the chance to clone? Lets say I keep a fossil server
>> runnin
Hi,
I know I've asked about this before, and thought I had gotten it right, but
after playing with the user capabilities the other day (and changing them
all), I was trying to set them back, and got stucked with the blues again.
I try to make public my resume in pdf (but not the latex sources).
O
eader.
2014-08-22 10:51 GMT-04:30 Richard Hipp :
>
>
>
> On Fri, Aug 22, 2014 at 10:17 AM, Abilio Marques > wrote:
>
>> Hi,
>>
>> I know I've asked about this before, and thought I had gotten it right,
>> but after playing with the user capabili
Tested what you said Mr. Hipp, didn't work that way either
2014-08-22 13:41 GMT-04:30 Ron W :
> On Fri, Aug 22, 2014 at 12:28 PM, Abilio Marques > wrote:
>
>> The file is only downloadable without login if checkout is set to nobody,
>> and not downloadable if set t
lio+Marques.en.pdf and also
/resume/doc/es-rel/Abilio+Marques.es.pdf (see the different directories),
leading me to believe that it also matches / characters. Is that the
expected behavior?
2014-08-22 20:00 GMT-04:30 Richard Hipp :
>
>
>
> On Fri, Aug 22, 2014 at 8:24 PM, Abilio Marq
Hi,
In a couple of hours I will lose access to this email address forever. I
want to switch this list to my personal email, abili...@gmail.com . I'm
notifying to see if there is someone that has to change it manually, or
I'll just re register.
Thanks,
Abil
Hi,
To make a long story short, I've always desired to run a script on a hook
feature. After a few times needing it, I decided to make a version of it
myself (I think some people had done this in the past).
I remember talking with someone about this feature (a few days ago I
thought it was with D
Here the current code (missing the capture of the stdout). I send it as a
patch to the current trunk version (0d1d7f6481).
Ideas?
On Sat, Jan 31, 2015 at 9:56 AM, Stephan Beal wrote:
> On Sat, Jan 31, 2015 at 3:09 PM, Abilio Marques
> wrote:
>
>> I think that adding the abi
Ohhh, I missed the attach in the first mail anyway, here it is:
http://abiliojr.homenet.org:20001/public/exec.diff
On Thu, Feb 5, 2015 at 11:41 AM, Stephan Beal wrote:
> On Thu, Feb 5, 2015 at 5:09 PM, Abilio Marques wrote:
>
>> Here the current code (missing the capture of th
Yeah, missed the attach...
On Thu, Feb 5, 2015 at 11:39 AM, Abilio Marques wrote:
> Here the current code (missing the capture of the stdout). I send it as a
> patch to the current trunk version (0d1d7f6481).
>
>
> Ideas?
>
> On Sat, Jan 31, 2015 at 9:56 AM, Stephan Beal
s and criticism are welcomed!
http://abiliojr.homenet.org:20001/public/execcmd.diff
On Thu, Feb 5, 2015 at 12:11 PM, Ron W wrote:
> On Thu, Feb 5, 2015 at 11:09 AM, Abilio Marques
> wrote:
>
>> Here the current code (missing the capture of the stdout). I send it as a
>>
You can hook the commit: admin>transfers>commit , but you'll need a way to
make it copy the files. I have a similar setup with LaTeX generating a PDF
every time I commit a change to the source. For this purpose I built an
exec command for TH1. By pure luck I've just sent a patch for my latest
versi
Hi,
I'm using fossil on an openshift gear (www.openshift.com), but I get this
error:
*home directory /var/lib/openshift/54fb48714382ecec88eb/ must be
writeable*
I hacked it by running:
*$HOME=. ./fossil command* (yeah, I downloaded the binary and put it into
the same directory)
But I d
Typo correction: I meant
HOME=. ./fossil command
>
On Wed, Mar 18, 2015 at 6:34 PM, Abilio Marques wrote:
> Hi,
>
> I'm using fossil on an openshift gear (www.openshift.com), but I get this
> error:
>
>
> *home directory /var/lib/openshift/54fb48714382ecec88eb/
Shouldn't unpublish show those check-ins still not pushed to the remote in
case a remote exist? Specially useful with autosync=0
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/foss
ings. I believe I've gone over it every
time I run fossil help, but never stopped to learn more about it, so thanks
for opening my eyes.
On Thu, Mar 19, 2015 at 4:14 PM, Warren Young wrote:
> On Mar 18, 2015, at 5:04 PM, Abilio Marques wrote:
>
>
> *home directory /var/lib/o
ote:
> On Mar 18, 2015, at 5:08 PM, Abilio Marques wrote:
> >
> > HOME=. ./fossil command
>
> Here’s a thought: Someone on this list gave me the idea of aliasing
> “fossil” to “f”. I do it with a symlink instead of a shell alias so that
> it works even in places l
Not that I'm aware of. I did some googling, and only found upset people,
but no justification, nor any kind of special commands.
On Thu, Mar 19, 2015 at 5:54 PM, Ron W wrote:
> On Thu, Mar 19, 2015 at 6:14 PM, Abilio Marques
> wrote:
>
>> But you're right, now that
ly from bed. Please excuse brevity and
> typos.
> On Mar 19, 2015 11:24 PM, "Ron W" wrote:
>
>> On Thu, Mar 19, 2015 at 6:14 PM, Abilio Marques
>> wrote:
>>
>>> But you're right, now that I think about it, is the only time I've ever
>>
history is stored in a place where the user cannot
> >> access/edit it).
> >>
> >> - stephan
> >> Sent from a mobile device, possibly from bed. Please excuse brevity and
> >> typos.
> >> On Mar 19, 2015 11:24 PM, "Ron W" wrote:
This email has two "motivations".
First:
Through the years I've evangelized about several subjects. Most of them go
hand in hand with my philosophy that software tools (well, this is
applicable to everything in life) should be as simple as possible for the
task they are intended to be used. Actu
l I survive this"
moment, but then they discover they can turn it off, use it for a while
like that, then give it a shot again, and then live with it (some love it).
On Thu, Mar 19, 2015 at 7:52 PM, Scott Robison
wrote:
> On Thu, Mar 19, 2015 at 6:14 PM, Richard Hipp wrote:
>
>
rote:
> On Thu, Mar 19, 2015 at 5:14 PM, Richard Hipp wrote:
> > On 3/19/15, Abilio Marques wrote:
> >>
> >> Most of the friends I've shown fossil to love the idea of having SCM,
> wiki
> >> and tickets in the same, tiny place. Looks prom
will only commit changes in 1, and if you do git status, will tell you
about the modifications done in 3.
On Thu, Mar 19, 2015 at 8:38 PM, Richard Hipp wrote:
> Further questions about staging area:
>
> If I do this:
>
> (1) Edit file xyzzy.txt
> (2) git add xyzzy.txt
> (3) Mor
. See
my next email
On Thu, Mar 19, 2015 at 9:01 PM, Andy Bradford <
amb-sendok-1429407112.filllmkhpgbjfacbk...@bradfords.org> wrote:
> Thus said Abilio Marques on Thu, 19 Mar 2015 19:22:14 -0430:
>
> > Having said these things, I must confess that in my mind, I find the
> &g
git commit -m "this is a test"
echo "line 2" >> test.txt
git status # You'll see it talks about unstaged changes by this point
git commit -m "another line in the test" # I believe it will refuse
On Thu, Mar 19, 2015 at 9:17 PM, Andy Bradford
wrote:
> Thus s
t are meant for other purposes. Fossil should keep away from
that road of uncertainty.
On Thu, Mar 19, 2015 at 8:28 PM, Andreas Kupries
wrote:
> On Thu, Mar 19, 2015 at 5:14 PM, Richard Hipp wrote:
> > On 3/19/15, Abilio Marques wrote:
> >>
> >> Most of the frien
ds, why?
just use the word STAGE). Believe me, reading about staging area seemed
weird and hard to grasp... why would I complicate with those things? In the
end I learned how to use it, and it improved communication with my team.
That's the reason why I tell you to give it a shot.
On Thu, M
After reading Mr. Hipp answer to some previous email about git saying:
So the staging area is being used as a way of working around the fact
that Git does not allow multiple independent check-outs against the
same repository? Am I understanding that correctly?
I started to think: what does it me
19, 2015 at 10:57 PM, Richard Hipp wrote:
> On 3/19/15, Abilio Marques wrote:
> > After reading Mr. Hipp answer to some previous email about git saying:
> >
> > So the staging area is being used as a way of working around the fact
> > that Git does not allow multi
Warren, thanks for your reply. It was pretty comprehensive, and I liked it,
even when those are bad news. I actually discovered some of them myself a
long time ago... Same goes to GIT, That's the reason I've only toyed with
the idea, but then started to think about the many many things that have t
After a yesterday's email entitled “is this a crazy idea?” meant to ask
about a shim ended in a really interesting discussion about select specific
changes to files, I think we could give that idea a chance to live (just as
an idea, for the time being).
I've personally gone through times where I
d would like to
> separate them so that Feature B is held back, Feature A is applied
> (and yes, tested, etc., etc) and committed, then Feature B is applied
> (tested, etc.) and committed ?
>
> Or am I misunderstanding ?
>
> -bch
>
>
> On 3/20/15, Richard Hipp wrote:
>
Let's forget the GIT staging area, I believe most of us, fossil users, have
proven that is not needed at all. Years and years committing without
staging, that proves is not needed ;)
On Mar 20, 2015 10:51 AM, "Kevin Greiner" wrote:
> On Fri, Mar 20, 2015 at 12:56 PM, Abilio
Ok, in an attempt to provide a short example:
The code is working, I have tests, yet I don't test for memory leaks.
That's my current scenario. A code snippet follows:
void functionA() {
char *thisWillLeak;
...
thisWillLeak = malloc(1024);
...
// never free nor return the memory
}
vo
But sometimes the subset of files to include in the first commit is longest
than the ones to be included in the second... so perhaps something like
fossil ci -m "first commit" --ignore file1 file2
would be easier than:
fossil ci -m "first commit" file3 file4 file5 file6... file12
On Fri, Mar 20
sk me for, until I'm ready to go to
the trunk.
On Fri, Mar 20, 2015 at 2:25 PM, Richard Hipp wrote:
> On 3/20/15, Abilio Marques wrote:
> > But sometimes the subset of files to include in the first commit is
> longest
> > than the ones to be included in the second... so
Hi,
I'm using fossil as usual, for my personal projects. This week I've been
working on a Unity game. I set up the fossil database as WAL using fossil
rebuild command. Now I get this every time I cancel a commit of a file that
includes binary data:
$ fossil ci -m "improving icon"
./scenes/mainSc
Hi,
I keep the main storage for my repos in a directory called ~/.fossilrepos .
I've been using for a few years now:
fossil server ~/.fossilrepos (with nohup)
And it works perfectly. Yet, today I was trying to use the --files option.
I first made an experiment with something like:
fossil server
I first understood that the restrictions were on the URL only, but yeah,
it's imaginable that they will be applied to the path too.
On Thu, Apr 23, 2015 at 6:34 AM, Richard Hipp wrote:
> On 4/22/15, Abilio Marques wrote:
> > Hi,
> >
> > I keep the main storage f
T
his is a thing I normally go through, and I believe is a silly question,
but I've read the entire help once again looking for it, and didn't find
it. Sometimes I do things like:
$fossil update d04e
UPDATE test.txt
---
On my previous email I said I was looking for a feature in the help. While
being at it, I found out these two details that I want to report.
But first, I want to say something about the help/documentation. One of the
things I LOVE about fossil is the simplicity. No weird, ultra-hidden
cryptic comm
+1. Been there, two times just in the last week (I need to sleep better).
On Thu, May 7, 2015 at 7:51 PM, Andy Goth wrote:
> I propose extending [fossil changes] to report when a file's execute bit
> has changed or it has become a symlink or ceased to be a symlink.
>
> For various annoying reaso
I normally undo or stash... I was just checking if I had missed something ;)
On Fri, May 8, 2015 at 2:21 PM, Warren Young wrote:
> On May 8, 2015, at 12:32 PM, Andy Bradford
> wrote:
> >
> > fossil undo
>
> Or “fossil stash”, if you don’t want your work thrown away, but can’t
> check it in yet.
Ohhh, I did use dbstat the other day (several times actually) while working
with some binary files. But yeah, I know there is the -a list, plus the
hidden list. But I'm still happy to know that almost everything I use is at
hand, and that I don't need a cryptic combination or plainly wrong named
co
y 8, 2015 at 2:31 PM, jungle Boogie
wrote:
> Hi Abilio,
> On 7 May 2015 at 19:19, Abilio Marques wrote:
> > T
> > his is a thing I normally go through, and I believe is a silly question,
> but
> > I've read the entire help once again looking for it, and didn
After using git for a while with a group of other 5 people who sometimes
forgot our policy that only one of us had the authority (actually the
responsibility) to work with the "master" branch, having to clean each
"mistake" later, we discovered the platform we had been using actually
offered a feat
> Note also that this goes against one of the founding principles of
> Fossil: that the VCS should implement mechanism not policy. That is
> to say, details of who should be able to check-in to which branches
> and whatnot should not be enforced by the VCS. Project policies need
> to be enforced
rote:
>
> On May 11, 2015 8:40 AM, "Andy Goth" wrote:
> >
> > On 5/11/2015 9:10 AM, Richard Hipp wrote:
> > > On 5/11/15, Abilio Marques wrote:
> > >> I recall seeing no way of detecting a "push" to a specific
> > >> branch.
Yeah, I know, this is about fossil, but I want to mention this, at it seems
an useful idea for people who uses binary files all the time.
https://git-lfs.github.com/
As far as I can see, binary files get uploaded into a web server using PUT,
and then a reference is made into the repo. That way gi
I know, I know, here we go again looking to git, but this is a question
concerning clean comments on commits.
When using git, you're suggested to write comments in the form of:
Subject Line (recommended as short, 50 to 75 characters long single line)
Description (whatever you want to put here)
way. Also, the tooltip can be drawn in a
more beautiful way (e.g., http://www.menucool.com/tooltip/css-tooltip)
Can anyone else see the usefulness of this idea (if also available in the
command line)?
On Wed, Nov 25, 2015 at 7:46 PM, Abilio Marques wrote:
> I know, I know, here we go again looking to gi
>
>
> ...
>
> i believe fossil should always display (in CLI mode) exactly what was
> input, without any sort of reformatting.)
But actually that's not the case. Fossil doesn't show at least newlines
(making a long comment a huge blob).
Yeah, I tried the css trick
early yesterday
,
72 matches
Mail list logo
