-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Gé Weijers email: g...@weijers.org mailto:g...@weijers.org
___
fossil-users mailing list
fossil-users@lists.fossil
-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
--
Gé Weijers email: g...@weijers.org mailto:g...@weijers.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org
Hi,
I decided to configure a repo for access by a few people only. I took
away all privileges for the 'nobody' and 'anonymous' users. Result: your
have to authenticate first.
The one annoyance is that the RSS feed still shows the titles of
individual commits. I don't think it's correct to do
And thank you for the fix in
http://fossil-scm.org/index.html/ci/78a6270fdc
Ge'
On Thu, 2010-02-04 at 21:40 -0800, Gé Weijers wrote:
Hi,
I decided to configure a repo for access by a few people only. I took
away all privileges for the 'nobody' and 'anonymous' users. Result: your
have
On Sun, 4 Apr 2010, D. Richard Hipp wrote:
I argue that abandoned branches are part of the historical record and
ought to be preserved. Fossil does distinguish between Open and
Closed branches. The user interface currently displays all branches
on the same page, but if it got to be a
working. That's not exactly trivial.
I work in a heavily regulated industry, and legal concerns have been
keeping us from implementing any and all DVCSes until now.
Gé
--
--
Gé Weijers g...@weijers.org___
fossil-users mailing list
fossil-users
I add the capabilities I remove from Adnonymous and Nobody to 'Reader',
and give all legitimate users either 'Reader' or 'Developer' access.
Gé
On Thu, 8 Apr 2010, Joshua Paine wrote:
On 04/08/2010 04:57 PM, Wes Freeman wrote:
- Is there a way to host a repository publicly, but make it so
Hi,
Is there any way to get fossil to validate (check the hash) of every
single artifact?
Ge'
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
After you merge in changes from a different branch, but before you check
in the merge, is there any way to back out the merge? fossil revert
undoes the changes but leaves the files edited, although with no
changes.
fossil undo
type fossil help undo for an explanation
Ge'
I would suggest running the problematic fossil command and capturing the
system call trace using 'strace -o LOG fossil cmd'. It's usually easy
enough to figure out the problem from the last dozen or so lines from the
'LOG' file.
Ge'
___
On Sun, 6 Mar 2011, David Bovill wrote:
My bash scripting is very basic. I've been trying to create some cgi's on
the server that will let me create new fossil repos. I've this test cgi, and
am unable to issue the commands to fossil that I am able to in the
terminal.
fossil sees that the
Nolan,
That should work just fine. I would put the closed-source variant in a
separate branch, so they can pull your changes and either merge wholesale
or cherrypick at will.
Ge'
On Wed, 25 May 2011, Nolan Darilek wrote:
A commercial company is interested in productizing one of my open
fossil built from the tip has mismatched versions of these two files.
The version numbers do not match, and therefor 'fossil sqlite3' is not
working.
Gé___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
You're right, thanks. 'touch src/sqlite3.h' followed by a 'make' does not
cause any files to be rebuilt. That explains it.
Gé
On Mon, 27 Jun 2011, Richard Hipp wrote:
On Mon, Jun 27, 2011 at 6:41 PM, Gé Weijers g...@weijers.org wrote:
fossil built from the tip has mismatched versions
The old tar 'v7' format only supports file names up to 99 characters,
according to the GNU tar documentation.
The check in 'tar_add_header' (tar.c) checks for nName 100.
The file name that gets mangled is exactly 100 chars long
Gé
On Mon, 18 Jul 2011, Rene wrote:
On Mon, 18 Jul 2011
I have submitted a bug report on this issue. The 'tar' format has been
extended over the years, and it's now a fairly interesting mess.
File names over 100 bytes are split into two. Posix requires this to be
done at a '/' (which you can delete). Fossil splits it anywhere, which
confuses all
On Thu, 21 Jul 2011, Rene wrote:
Thanks for the bug report. I wonder are you able to get the same
(mis)behavior
out of fossil as I did out of my repository?
Yes, it's reproducible. Once the file path length goes over 100 characters
the file quite reliably does not come out right. All the
Hi,
I have just committed a fix for issues with long path names when Fossil
generates a tar file. What first looked simple wasn't because of backward
compatibility requirements. You can find my work in branch 'ge-tarfix'.
I have attempted to use the rules laid out on the latest POSIX.1
On Mon, 25 Jul 2011, Russ Paielli wrote:
And [Fossil] is reported to destroy repositories if someone branches:
http://sheddingbikes.com/posts/1306005291.html
I expect that mr. Shaw will shoot himself in the foot using git rebase
or git push --force one day and abandon git for something
On Tue, 9 Aug 2011, Richard Hipp wrote:
Change the subject: Please help me to understand why people want to create a
new branch before adding
changes to that branch, rather than just waiting until they check-in their
edits? I'm not being
sarcastic or critical here. A lot of people do
On Tue, 9 Aug 2011, Lluís Batlle i Rossell wrote:
If you could just tell fossil that you intend to commit to a new
branch from the current workspace/checkout creating that extra
commit object could be avoided without risking a commit to the wrong
branch.
You can *later* change the branch,
On Tue, 9 Aug 2011, Richard Hipp wrote:
On Tue, Aug 9, 2011 at 2:33 PM, Gé Weijers g...@weijers.org wrote:
If you create the branch first you cannot forget later and commit to the wrong
branch.
I beg to differ! Just this past Friday, I did three separate commits to SQLite
that went
On Wed, 17 Aug 2011, Christopher Vance wrote:
How about fossil test-integrity?
fossil: checksum mismatch on blob rid=7657:
da39a3ee5e6b4b0d3255bfef95601890afd80709 vs
76ce4c2d48d71c1c50113303fa40dbf1805bfad7
But I also notice that a fresh clone from www.fossil-scm.org on two
different OSs
On Fri, 12 Aug 2011, Jos Groot Lipman wrote:
One question that pops up: why/when would I close a leaf.
I mostly do it to make non-active branches no longer show up in the UI
and as the result of some command lines (fossil leaves).
I use feature branches a lot, and when I'm done with one I
On Sat, 20 Aug 2011, Vikrant Chaudhary wrote:
Timestamps should be recorded in local timezone rather than in UTC.
1. It hurts eyes and brain to see the time in UTC and then calculate
it in local time.
2. For forensics. I'll be able to know which timezone I was while
committing that change.
On Fri, 26 Aug 2011, Gilles wrote:
I'm not very clear at what a manifest is:
www.sqlite.org/debug1/doc/trunk/www/fileformat.wiki
It seems to be a list of artifacts (ie. changes?) for each file under
source control.
The manifest describes a committed revision. It's mostly file names and
My guess:
because you're running as root fossil locks itself in a 'chroot' jail. Try
creating a directory 'root' in the directory your repository lives in, and
make sure the owner of the repository can write to that directory. Or you
can set HOME=/ which sets the home directory to the root of
On Sat, 10 Sep 2011, Richard Hipp wrote:
The hook mechanism should include a delay. This is because client-to-server
push operations can occur in multiple stateless steps, and we really want to
wait and
run the hooks after all steps of the push operation are complete. So, for example,
Hi,
Is there any way I can get fossil to ignore all the CVS directories and
anything under it? I can't seem to get ignore-glob to do anything useful
here.
Thanks,
Gé___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On Fri, 16 Sep 2011, Richard Hipp wrote:
time(0) should give you UTC directly. No need to convert.
This is the common implementation, but not required by any standard. Most
OSes do it this way, but POSIX and C99 do only require that time_t be an
integer or real type (so it could be a
Stephan,
'mktime' converts localtime, it's not designed to do what you want it to
do. Setting is_dst just sets the assumption about whether DST is in
effect. Setting it to -1 makes the routine look it up. I don't know what
happens in that one 'ambiguous' hour each year.
use the result of
time(0). It doubt there's a system out there that can compile Fossil _and_
uses a different representation of time.
Gé
On Sat, 17 Sep 2011, Stephan Beal wrote:
On Sat, Sep 17, 2011 at 12:25 AM, Gé Weijers g...@weijers.org wrote:
long UnixTime(time_t now
On Mon, 3 Oct 2011, Lluís Batlle i Rossell wrote:
Additionally, I don't know how portable it is to use always getaddrinfo
(POSIX-2001?) while requiring C89.
C89 does not address networking, so this issue is unrelated to C89. If
getaddrinfo is not supported on a platform that uses the
Hi Ashish,
On Wed, 5 Oct 2011, Ashish SHUKLA wrote:
I wasn't aware of both sockaddr_storage, and getnameinfo(). They seem good to
me, and I've updated diff[1] to use them.
References:
[1] http://people.freebsd.org/~ashish/fossil-ipv6-rev-proxy.diff
A few comments (not all about your
On Wed, 5 Oct 2011, Michal Suchanek wrote:
And when you find an issue with a commit that is some way back in your
personal branch it is more logical and easier to review your branch if
you append the fix to the commit where it belongs logically or if you
append it at the top of the history
The best way to handle this is to use getaddrinfo and getnameinfo,
deal with multiple sockets and be blissfully unaware of the actual
protocol being used in 99% of the code. All the #if stuff is a pain to
deal with.
-- Gé
On Oct 16, 2011, at 18:59, Christopher Vance cjsva...@gmail.com wrote:
I
One approach I have seen is to add a link that when traversed classifies
the IP address as belonging to a robot. It could be put on the timeline
page, preceded by a warning not to follow the link.
--
Gé
___
fossil-users mailing list
On Sunday, January 8, 2012, Russ Paielli wrote:
I am wondering about fossil/git interaction. Everyone else seems to be
using git and github. I see that fossil can import from, and export to,
git. If I understand it correctly, however, that is only for creating a new
fossil or git repository.
On Mon, Feb 13, 2012 at 1:49 PM, Steve Bennett ste...@workware.net.auwrote:
Joe Mistachkin has recently added support for calling TH1 scripts on
certain actions.
See http://www.fossil-scm.org/index.html/info/0b61e3c019
In the jimtcl branch, TH1 is replaced with Jim Tcl, so any of these
To prevent stupid stuff from happening fossil could (on (Lin|Un|Pos)ix at
least) track whether any file it manages shows up twice by looking at the
output of the stat() system call:
if (S_ISREG(statdata.st_mode) statdata.st_nlink 1) {
if (seen_before(statdata.st_dev, statdata.st_ino))
On Fri, May 25, 2012 at 10:59 AM, Ron Wilson ronw.m...@gmail.com wrote:
On top of that, could support signing one or more of the existing
signatures at the time of signing.
When I sign a commit, it can mean multiple things:
1) I wrote this (authentication)
2) I approve this (authorization)
In
On Wednesday, September 5, 2012, E. Timothy Uy wrote:
In case anyone ever runs into this issue (an xinetd env issue), the
solution is to add the following to your service:
server = /usr/local/bin/fossil
server_args = http REPOSITORY
env = TZ=PST8PDT (insert your timezone here)
I suggest
Try CC=gcc ./configure before you run 'Make'. The autoconfig tool uses
cc, which is an alias for the 'clang' compiler frontend.
On Mon, Mar 25, 2013 at 11:14 AM, Stephen De Gabrielle
stephen.degabrie...@acm.org wrote:
Thanks, I did install the CL tools, but something is clearly awry if its
43 matches
Mail list logo
