2015-02-24 20:37 GMT+01:00 bch brad.har...@gmail.com:
Tags are symbolic names that may or may not be propagate -- a branch
name is an example of a propagating tag, and a non-propagating tag may
be (for example) a tag that marks a specific commit as a release
(see:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/24/2015 3:21 PM, Ron W wrote:
Took a quick look at Fossil commits tagged release, I see tags
like version-1.31, version-1.30, etc. I also see references to
SQLite versions in the form x.y.z as opposed to a date string.
Seems like x.y or
Am Tue, 24 Feb 2015 12:04:06 -0500
schrieb Ron W ronw.m...@gmail.com:
But, in any case, Mr robotanarchy seems to be requesting that the
official release tar file be created with, for example:
fossil tarball version-1.31 fossil-src-1_31.tar.gz --name
fossil-src-1_31
to make it
Hi Joe,
On 24 February 2015 at 12:38, Joe Prostko joe.pros...@gmail.com wrote:
I think this is mostly handy for packagers, where it's easier to write
a packaging script knowing the downloaded file will be
somepieceofsoftware-1.2.3.tar.gz, which then extracts out to
somepieceofsoftware-1.2.3.
On Tue, Feb 24, 2015 at 4:21 PM, Ron W ronw.m...@gmail.com wrote:
Took a quick look at Fossil commits tagged release, I see tags like
version-1.31, version-1.30, etc. I also see references to SQLite
versions in the form x.y.z as opposed to a date string.
BTW, would be useful to have an entry
Seen with Fossil 1.29, and reproduced
with b0febccc4e1cf5c6763e3aa088b1ea788d255e47 (2015-02-24 06:03:54).
Summary:
I created a new branch, and in the new branch:
- Committed a rename of file A to B.
- Committed an add of a new file A.
- Committed changes to files A and B.
Then I merged the
you're right, my mistake -- closed is what I meant, but didn't
describe properly. :P
On 2/24/15, Jan Nijtmans jan.nijtm...@gmail.com wrote:
2015-02-24 20:37 GMT+01:00 bch brad.har...@gmail.com:
Tags are symbolic names that may or may not be propagate -- a branch
name is an example of a
Hi Ron,
On 24 February 2015 at 13:24, Ron W ronw.m...@gmail.com wrote:
BTW, would be useful to have an entry in the search type pull-down for tags
(there were a lot of occurrences of release in the comments).
Although not exposed as a menu option there is this link:
On Tue, Feb 24, 2015 at 3:59 PM, jungle Boogie jungleboog...@gmail.com
wrote:
How have you been updating packages in the past?
All releases are like this:
20150223162734
20150119112900
20140612172556
20140127173344
2013094349
Took a quick look at Fossil commits tagged release, I see
On Tue, Feb 24, 2015 at 3:11 PM, Richard Hipp d...@sqlite.org wrote:
On 2/24/15, robotanarchy robotanar...@bingo-ev.de wrote:
I'd replace the underscore with a dot, so it becomes
fossil-1.31.tar.gz
..but other than that, that's my point.
Can you guys do that?
We can call things
On Tue, Feb 24, 2015 at 3:55 PM, Svyatoslav Mishyn j...@openmailbox.org
wrote:
BTW, the manual page is not installing by the command ```make install```
There isn't one to install.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
Freedom is sloppy. But
So, got some time into things, it seems to me, that the fossil config
import command does not work properly.
My Testcase:
beowulf@PowerWolf:~$ fossil init repoA.fossil
project-id: c3c22922a11b4a6536af4c2506369f3926ae1d1f
server-id: b7e6a9010387a9ea7d163c9f40c8a274192a9989
admin-user: user
Hello,
Index: src/browse.c
==
--- /home/juef/fossil/e/fossil/src/browse.c~0 2015-02-24 16:31:46.677114589
+0200
+++ /home/juef/fossil/e/fossil/src/browse.c 2015-02-24 16:21:11.700411735
+0200
@@ -1035,7 +1035,7 @@
@
Maybe I missed something, but the help states fossil import overwrites by
default, doesn't it? Also there is nothing mentioned about that parameter
in the import command.
beowulf@PowerWolf:~$ fossil help config import
Usage: fossil configuration METHOD ... ?OPTIONS?
Where METHOD is one of:
On 2/24/15, Oliver Friedrich redtalonof+mailingl...@gmail.com wrote:
So, got some time into things, it seems to me, that the fossil config
import command does not work properly.
My Testcase:
beowulf@PowerWolf:~$ fossil init repoA.fossil
project-id: c3c22922a11b4a6536af4c2506369f3926ae1d1f
Hello Fossil developers,
I was building the fossil binary yesterday and I've noticed that the
names of the tarballs aren't very userfriendly.
As I see it, there are two tarballs that one could use, one is from the
downloads page [1] and one is by using some strange SHA1 hash of the
release, as
On 2/24/15, robotanarchy robotanar...@bingo-ev.de wrote:
Hello Fossil developers,
I was building the fossil binary yesterday and I've noticed that the
names of the tarballs aren't very userfriendly.
As I see it, there are two tarballs that one could use, one is from the
downloads page [1]
Am Tue, 24 Feb 2015 15:33:42 +0100
schrieb Stephan Beal sgb...@googlemail.com:
On Tue, Feb 24, 2015 at 3:30 PM, Richard Hipp d...@sqlite.org wrote:
Providing a date on the filename seems (to me) a lot more useful
than a random SHA1 hash.
+1, if only because they retain their release
Just to throw my thought on this into the discussion.
I'd really appreciate having a static url to get the latest stable/testing
sources from.
So to be able to download from
https://www.fossil-scm.org/download/fossil-src-stable.tar.gz the latest
stable sources.
Maybe that even makes it
On 2/24/15, Oliver Friedrich redtalonof+mailingl...@gmail.com wrote:
Just to throw my thought on this into the discussion.
I'd really appreciate having a static url to get the latest stable/testing
sources from.
https://www.fossil-scm.org/fossil/tarball/fossil-src-stable.tar.gz?uuid=release
On 2/24/15, Oliver Friedrich redtalonof+mailingl...@gmail.com wrote:
Interesting thing, still the two demo repositoris repoA and repoB.
Both fired up with fossil ui repo[AB].fossil, then using the web frontend
to change password of the default user to 123. Then the repos will both
have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
$ tar tzf fossil-src-20150223162734.tar.gz | head -1
fossil-src-201502231627/
Unlike previous releases, the unpacked directory name does not contain the
seconds. This means the directory and archive filenames don't match, which is
a problem for
On Tue, Feb 24, 2015 at 5:01 PM, Richard Hipp d...@sqlite.org wrote:
On 2/24/15, Oliver Friedrich redtalonof+mailingl...@gmail.com wrote:
I'd really appreciate having a static url to get the latest
stable/testing
sources from.
On Tue, Feb 24, 2015 at 03:52:56PM +, Oliver Friedrich wrote:
Just to throw my thought on this into the discussion.
I'd really appreciate having a static url to get the latest stable/testing
sources from.
So to be able to download from https://www.fossil-scm.org/download/
Interesting thing, still the two demo repositoris repoA and repoB.
Both fired up with fossil ui repo[AB].fossil, then using the web frontend
to change password of the default user to 123. Then the repos will both
have different hashes for the passwords. Seems the password hashes get
somehow
2015-02-24 15:30 GMT+01:00 Richard Hipp d...@sqlite.org:
On 2/24/15, robotanarchy robotanar...@bingo-ev.de wrote:
Hello Fossil developers,
I was building the fossil binary yesterday and I've noticed that the
names of the tarballs aren't very userfriendly.
As I see it, there are two tarballs
On 2/24/15, Andy Goth andrew.m.g...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
$ tar tzf fossil-src-20150223162734.tar.gz | head -1
fossil-src-201502231627/
Unlike previous releases, the unpacked directory name does not contain the
seconds. This means the directory and
On Tue, Feb 24, 2015 at 11:27 AM, Baptiste Daroussin
baptiste.darous...@gmail.com wrote:
2015-02-24 15:30 GMT+01:00 Richard Hipp d...@sqlite.org:
On 2/24/15, robotanarchy robotanar...@bingo-ev.de wrote:
When downloading file [1], you'll get an archive that has a different
file name than
Hi,
What does selecting Tags in Timeline actually do? I was expecting to see
the list of non-propagating tags but I don't understand how I could use the
output I see.
Also, what does unhide actually do? Why do I need to explicitly click
unhide to see any output on this page:
On Tue, Feb 24, 2015 at 12:02 PM, Richard Hipp d...@sqlite.org wrote:
On 2/24/15, Andy Goth andrew.m.g...@gmail.com wrote:
Unlike previous releases, the unpacked directory name does not contain the
seconds. This means the directory and archive filenames don't match, which
is a problem for
On 2/25/15, Marcus Lam marcus...@outlook.com wrote:
Noted.
On the Fossil Concepts page, under section 4.2 Manual-Merge Workflow, at
step 8 there is a typo of use use.
Thanks. Should be fixed now.
--
D. Richard Hipp
d...@sqlite.org
___
Hi Stephan,
On Feb 24, 2015 5:47 PM, Stephan Beal sgb...@googlemail.com wrote:
On Wed, Feb 25, 2015 at 2:32 AM, jungle Boogie jungleboog...@gmail.com
wrote:
Are these two supposed to match? should the compression ratio be the
same for my clone vs, website report?
They should be identical -
Hello All,
Se we have this command:
https://www.fossil-scm.org/fossil/help?cmd=dbstat
And this for web UI:
https://www.fossil-scm.org/fossil/help?cmd=/stat
Fossil repo stats: https://www.fossil-scm.org/fossil/stat
Are these two supposed to match? should the compression ratio be the
same for my
On Wed, Feb 25, 2015 at 2:32 AM, jungle Boogie jungleboog...@gmail.com
wrote:
Are these two supposed to match? should the compression ratio be the
same for my clone vs, website report?
They should be identical - the CLI command was initially derived from the
/stats page. It is possible that
On Wed, Feb 25, 2015 at 02:47:24AM +0100, Stephan Beal wrote:
On Wed, Feb 25, 2015 at 2:32 AM, jungle Boogie jungleboog...@gmail.com
wrote:
Are these two supposed to match? should the compression ratio be the
same for my clone vs, website report?
They should be
On Tue, Feb 24, 2015 at 3:59 PM, jungle Boogie jungleboog...@gmail.com wrote:
Hi Joe,
How have you been updating packages in the past?
All releases are like this:
20150223162734
20150119112900
20140612172556
20140127173344
2013094349
I just used those as they were without issue.
On Wed, Feb 25, 2015 at 3:25 AM, Martin Gagnon eme...@gmail.com wrote:
On Wed, Feb 25, 2015 at 02:47:24AM +0100, Stephan Beal wrote:
On Wed, Feb 25, 2015 at 2:32 AM, jungle Boogie
jungleboog...@gmail.com
wrote:
Are these two supposed to match? should the compression ratio be
On 2/24/15, Andy Goth andrew.m.g...@gmail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2/24/2015 3:21 PM, Ron W wrote:
Took a quick look at Fossil commits tagged release, I see tags
like version-1.31, version-1.30, etc. I also see references to
SQLite versions in the form
On 2/24/15, Ron W ronw.m...@gmail.com wrote:
[Managers] associate dates with deadlines, so version numbers remove
a source of panic.
Fair enough. I'll migrate from dates to version numbers in the next release.
--
D. Richard Hipp
d...@sqlite.org
___
On Tue, Feb 24, 2015 at 7:01 PM, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Feb 24, 2015 at 9:11 PM, Richard Hipp d...@sqlite.org wrote:
So it seems like having dates on the download would be more meaningful
than having a made-up version number. No? With a date, at least you
know
On 24 February 2015 at 16:50, Ron W ronw.m...@gmail.com wrote:
On Tue, Feb 24, 2015 at 7:01 PM, Stephan Beal sgb...@googlemail.com wrote:
On Tue, Feb 24, 2015 at 9:11 PM, Richard Hipp d...@sqlite.org wrote:
So it seems like having dates on the download would be more meaningful
than having a
On Tue, Feb 24, 2015 at 9:11 PM, Richard Hipp d...@sqlite.org wrote:
So it seems like having dates on the download would be more meaningful
than having a made-up version number. No? With a date, at least you
know about how old the code is. What information does a made-up
version number
Noted.
On the Fossil Concepts page, under section 4.2 Manual-Merge Workflow, at
step 8 there is a typo of use use.
Regards
Marcus Lam
Date: Wed, 25 Feb 2015 00:12:36 -0500
From: d...@sqlite.org
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] Newbie question - how to
On 2/25/15, Marcus Lam marcus...@outlook.com wrote:
Hi,
New to Fossil. Found a typo while reading the online Fossil Concepts page.
Want to raise a ticket for that but could not locate instruction for doing
so. Any pointer?
Email to this mailing list is the fastest way to get something
Hi,
New to Fossil. Found a typo while reading the online Fossil Concepts page.
Want to raise a ticket for that but could not locate instruction for doing so.
Any pointer?
Regards
Marcus Lam
___
On Tue, Feb 24, 2015 at 4:47 PM, Andy Goth andrew.m.g...@gmail.com wrote:
So just grab the file at this URL:
https://www.fossil-scm.org/fossil/tarball/fossil-1.31.tar.gz?uuid=version-1.31
and be happy. The file will have the name you want.
Or replace 1.31 with whichever tagged release
On Tue, Feb 24, 2015 at 5:16 PM, Richard Hipp d...@sqlite.org wrote:
It's going to be more complicated than that. The people who want
...
Since this is a major change, I propose that it be deferred until
Fossil 2.0 (which will likely be the next release).
Honestly, it doesn't matter to me.
47 matches
Mail list logo