Re: [fossil-users] Why Hash

[Jacek Cała]

2015-09-09 22:03 GMT+01:00 paul :

> On Wed, Sep 9, 2015 at 7:19 AM, Luca Ferrari 
> wrote:
>
>>
 Assuming I am remembering correctly, if Fossil had this feature, you
>>> could
>>> do something like:
>>>
>>> $ fossil timeline -N -n 3
>>> 0  [d28be5063a] *CURRENT* Fix linker parameter file
>>> 1  [10a5af61c1] Alt code for HS interface
>>> 2  [5250e3796e] Increase speed threshold
>>> $ fossil info 1
>>> uuid: 10a5af61c1fc25060ad428de9c82e3615b45f6c8 ...
>>>
>>> The numbers, of course, could change after any sync or commit.
>>>
>>

> Sounds to me like you need a GUI.
>>
>
> Some things are just more convenient with a GUI.
>
>
Personally, I don't think it is only the GUI thing. Fossil delivers both
sides: the CLI client and the server in a neat single exec file. The
ordered numbering is just a client-side convenience. Long time ago I was
trying to propose and (almost) implemented numbering for changes, so you
could do selective commit with range of files like 1-5,7. There was little
interest in that feature, so I gave up.

All in all, I think it would be nice to add these little things to the
console client, so the need for the GUI is only for those who really hate
console.

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Conflicts during update

[Jacek Cała]

Thanks Warren for valuable comments. I had to resolve the problem and
cannot easily revert to the suspicious state I had reported previously. I
wonder whether 'fossil stat' would give me the answer I was looking for.
Will remember it for the future.

  Cheers,
  Jacek

2015-08-12 21:12 GMT+01:00 Warren Young w...@etr-usa.com:

 On Aug 12, 2015, at 2:13 AM, Jacek Cała jacek.c...@gmail.com wrote:
 
  I work primarily on Windows and whenever fossil complains about CR/LF I
 just ignore it (saying 'a' during the commit).

 Don’t do that.

 Fossil is trying to tell you about a real problem.  It means you have
 either got:

 a. A file with mixed line ending styles (e.g. LF most places but CR+LF in
 a few places); or

 b. A text file using a line ending style inconsistent with your current
 Fossil settings.

 Instead of ignoring the warning, you should either:

 1. Decide that the project’s line ending style is CR+LF to cater to
 Windows defaults, then set the crnl-glob setting so that Fossil knows which
 files are text files, and thus don’t need this warning; or

 2. Choose LF instead, and use text editors on Windows that don’t rewrite
 LF files as CR+LF, and which visually warn you about mixed line endings.

 If you don’t make a decision and stick to it, you get two bad effects.
 First, you can’t tell case ‘a’ above from case ‘b’.  Second, you’re
 checking in a bunch of pointless diffs, potentially one per line, which
 makes automatic merging impossible.

 Option 2 is preferable, if you can get away with it.  Unless you’re still
 using Notepad, you probably *can* get away with it these days.

 If you must choose option 1 for some reason, I recommend that you use
 Fossil’s versioned crlf-glob setting.  (i.e. vi .fossil-settings/crnl-glob)

 One alternative is to set it via the Admin/Settings UI, but that only
 affects new clones; it doesn’t change the settings on sync in existing
 clones.

 The other alternative is to do it via the “fossil setting” command, but
 that’s unmaintainable and doesn’t let you easily use line breaks, which
 makes the *glob settings much more readable.

  I guess, there is no way to list files that were reported as conflicting
 during merge, is there?

 Except for the deleted files case brought up in my other post, Fossil
 tells you this at least two different ways:

 –  $ f update
   MERGE foo/bar.txt
   * 1 merge conflicts in foo/bar.txt
   
   updated-to:   99c79be1294d… etc.
   WARNING: 1 merge conflicts

 and, after an incomplete update:

   $ f stat
   repository: /path/to/repo.fossil
   …
   CONFLICT   foo/bar.txt

 This doesn’t currently (!) happen with the mv-rm-files enabled, if you
 said “fossil rm”.  Instead of CONFLICT, you get DELETED.
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Conflicts during update

[Jacek Cała]

Thanks for the suggestion... no luck in finding ''. It matches only
_FOSSIL_ and a few binary files. It could be the line endings because I
work primarily on Windows and whenever fossil complains about CR/LF I just
ignore it (saying 'a' during the commit).

However, I guess, there is no way to list files that were reported as
conflicting during merge, is there?

  Cheers,
  Jacek

2015-08-12 8:21 GMT+01:00 Stephan Beal sgb...@googlemail.com:

 On Wed, Aug 12, 2015 at 9:07 AM, Jacek Cała jacek.c...@gmail.com wrote:

   Hi All,

 I've done fossil update and got a suspicious message about merge
 conflicts (see below). The list of changes is long (21k), so I can't easily
 see all changes file by file and the last thousand is just ADDED or REMOVED.

 Is there a way I can check what merge conflicts fossil means in this
 case? A dumb search for word 'CONFLICT' in the source code does not show
 anything.


 Search for '' and ''

 As someone recently pointed out, if you have changed the line endings
 (from Windows to Unix or vice versa) between 2 versions, the whole file
 will be seen as changed, and could lead to confusing conflicts.

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
 those who insist on a perfect world, freedom will have to do. -- Bigby Wolf

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Conflicts during update

[Jacek Cała]

Hi Tomek,

As mentioned in my previous e-mail, in my case it was an issue with files
changed in my working copy which were deleted in the remote repo. Fossil
reported them as 'edited locally but deleted by update' and left them in my
working copy. I find it inconvenient because the only way I can think of to
resolve it is to do 'fossil undo', see the changes, address them and then
'fossil update' makes sense.

  Cheers,
  Jacek


2015-08-12 14:09 GMT+01:00 Tomek Kott tkott.onl...@outlook.com:

 So I've seen a very similar thing happen twice on a windows machine, where
 fossil reports conflicts in a lot of files (in one case it was binary code
 for LabVIEW, so no possible line endings) but individual inspection of
 differences with a proper binary differ listed nothing. Only a close/reopen
 cleared whatever was going on from fossil. I've never been able to track it
 down as a repeatable bug, but I do actually believe there might be some odd
 edge case.

 Tomek

  Date: Wed, 12 Aug 2015 10:19:33 +0200
  From: Stephan Beal sgb...@googlemail.com
  To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
  Subject: Re: [fossil-users] Conflicts during update
  Message-ID:
  CAKd4nAgMg13tA1k_-HPWP8hj6_zdR4P7C9yZEqf=zjwhp9h...@mail.gmail.com
  Content-Type: text/plain; charset=utf-8
 
  On Wed, Aug 12, 2015 at 10:13 AM, Jacek Ca?a jacek.c...@gmail.com
 wrote:
 
   Thanks for the suggestion... no luck in finding ''. It matches
 only
   _FOSSIL_ and a few binary files. It could be the line endings because I
   work primarily on Windows and whenever fossil complains about CR/LF I
 just
   ignore it (saying 'a' during the commit).
  
   However, I guess, there is no way to list files that were reported as
   conflicting during merge, is there?
  
 
  Not that i am aware of. i know svn requires one to manually tell it the
  conflict for this specific file is resolved, but fossil does not do so,
  and it does not remember that a file is conflicted. When a conflict
 occurs,
  the conflicting part(s) of the file will be wrapped up in blocks which
 look
  like this (copy/pasted from a recent mail by Richard):
 
   BEGIN MERGE CONFLICT: local copy shown first 
  === COMMON ANCESTOR content follows 
  === MERGED IN content follows ==
   END MERGE CONFLICT 
 
  If you don't see any of those in your source-controlled files then fossil
  does not know about a conflict. If it reports a conflict and yet does not
  tag it with such a block, then something is wrong (in fossil), but we are
  not currently aware of any such bugs.
 
  --
  - stephan beal
  http://wanderinghorse.net/home/stephan/
  http://gplus.to/sgbeal
  Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
  those who insist on a perfect world, freedom will have to do. -- Bigby
 Wolf
  -- next part --
  An HTML attachment was scrubbed...
  URL: 
 http://lists.fossil-scm.org:8080/pipermail/fossil-users/attachments/20150812/4bef1cf8/attachment.html
 
 


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] quick poll: do you generally use add/rm or mv

[Jacek Cała]

The same for me. I always use mv as, I guess, add/remove destroys the
history of changes.

Re syncing with the file system, I find it ok as it is. Usually, I move
files using IDE when coding, and then find missing ones while trying to
commit. For me 'mv' works ok with the exception that when I added a renamed
file, such that 'fossil chan' gives:

MISSING myfile-oldname.txt
ADDED myfile-newname.txt

fossil complains if I try to do

$ fossil mv myfile-oldname.txt myfile-newname.txt

and then I have to do

$ fossil rm newname.txt
$ fossil mv myfile-oldname.txt myfile-newname.txt

It would be perfect for me if I could just run the mv command even if the
renamed file was already added to the current change stack.

  Cheers,
  Jacek


2015-08-03 4:53 GMT+01:00 Stephan Beal sgb...@googlemail.com:

 Counterpoint: have never used addremove because (A) i invariably have lots
 of temp/scratch files and (B) it's a pretty alien feature (not existing
 anywhere else, AFAIK). i always use mv.

 - stephan
 Sent from a mobile device, possibly from bed. Please excuse brevity and
 typos.
 On Aug 3, 2015 01:22, Matt Welland mattrwell...@gmail.com wrote:

 I've been using (and advising others to use) addremove because fossil mv
 behavior did not match Unix mv. The differences were confusing. I've no
 idea if fossil mv now behaves exactly like mv. The other issue was that
 fossil move did not keep the filesystem in sync with fossil which is also
 confusing and error prone.

 On Sat, Aug 1, 2015 at 8:46 AM, Michai Ramakers m.ramak...@gmail.com
 wrote:

 Hello,

 I have been avoiding 'fossil mv' a bit until recently, because I
 didn't trust it for no good reason. I reckon since it is in trunk, it
 is considered stable.

 In project-trees here, I move/rename dirs and files quite often. What
 I did earlier, was simply to move them as per filesystem, and then let
 'fossil addremove' do its thing, and make a commit of only those
 additions/removals.

 I was wondering what you generally do for directory trees in motion -
 use add/rm or mv ? And: the benefit of fossil having a concept of
 'moved file/dir' is that the user can trace ancestry crossing
 moves/renames more easily, is that correct? (At least that's how I use
 it now.)

 Michai
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Issue with cloning a repo

[Jacek Cała]

As stated in the original question 'ssh SERVERNAME' works fine, which means
'ping SERVERNAME' can also resolve the name ok.

2015-06-17 13:44 GMT+01:00 Stephan Beal sgb...@googlemail.com:

 On Tue, Jun 16, 2015 at 5:44 PM, Jacek Cała jacek.c...@gmail.com wrote:

 works perfectly fine. It's not urgent for me because I can work using IP
 but I'd appreciate any hints how it may be solved.


 Try:

 ping SERVERNAME

 If that results in the same error then the problem is your DNS config or
 access to the DNS server.

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
 those who insist on a perfect world, freedom will have to do. -- Bigby Wolf

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Issue with cloning a repo

[Jacek Cała]

Hi,

Please find below some details about the software running in my container:

- fossil version -v says:
This is fossil version 1.33 [9c65b5432e] 2015-05-23 11:11:31 UTC
Compiled on Jun 10 2015 22:28:08 using gcc-4.6.3 (32-bit)
SQLite 3.8.10.2 2015-05-20 18:17:19 2ef4f3a5b1
Schema version 2015-01-24
zlib 1.2.3.4, loaded 1.2.3.4
SSL (OpenSSL 1.0.1 14 Mar 2012)
UNICODE_COMMAND_LINE

  It's been downloaded from the fossil download web page as the precompiled
binary for linux

- uname -a says:
Linux 7cf360a14afe 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux

  It's been downloaded from the DockerHub as the latest ubuntu version

- lsb_release -a says:

No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.2 LTS
Release:14.04
Codename:   trusty

- ssh client config has not be touched by me in any way.
- /etc/resolv.conf includes references to my organisation's DNS servers and
domain name (I wouldn't like to share it in public). However, it's
identical to my host machine where fossil clone works fine.

Finally, I ran in the container: apt-get update and installed a number of
packages, all went fine.

  Best,
  Jacek


2015-06-17 14:20 GMT+01:00 Jan Nijtmans jan.nijtm...@gmail.com:

 2015-06-16 17:44 GMT+02:00 Jacek Cała jacek.c...@gmail.com:
  Hi,
 
  I'm running fossil 1.33 in a docker container and found an issue when
  cloning my repo. If I run it like:
 
  $ fossil clone http://USERNAME@SERVERNAME/REPONAME repo.fossil

 What does fossil version -v say?  Or file fossil?

 Is the fossil binary self-compiled or obtained elsewhere?
 Is it a 32-bit or 64-bit binary, is it statically linked or not?

 Answers to those questions might give a hint on what's happening here.

 Regards,
  Jan Nijtmans
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Issue with cloning a repo

[Jacek Cała]

Thank you Jan for clarifying the problem.

BTW, perhaps that's a reason why on the download page there could also be a
linux-x64 version available.

  Cheers,
  Jacek


2015-06-17 15:17 GMT+01:00 Jan Nijtmans jan.nijtm...@gmail.com:

 2015-06-17 15:56 GMT+02:00 Jacek Cała jacek.c...@gmail.com:
  Hi,
 
  Please find below some details about the software running in my
 container:
 
  - fossil version -v says:
  This is fossil version 1.33 [9c65b5432e] 2015-05-23 11:11:31 UTC
  Compiled on Jun 10 2015 22:28:08 using gcc-4.6.3 (32-bit)
  SQLite 3.8.10.2 2015-05-20 18:17:19 2ef4f3a5b1
  Schema version 2015-01-24
  zlib 1.2.3.4, loaded 1.2.3.4
  SSL (OpenSSL 1.0.1 14 Mar 2012)
  UNICODE_COMMAND_LINE
 
It's been downloaded from the fossil download web page as the
 precompiled
  binary for linux

 Yes, that's what I thought.  When compiling fossil using the option
 -static,
 gcc gives the following warning:
 warning: Using 'getaddrinfo' in statically linked applications
 requires at runtime the shared libraries from the glibc version used
 for linking
 well, your docker container doesn't have the necessary 32-bit shared
 libraries ...

 There are two solutions:
 - compile fossil as 64-bit linux executable.
 - obtain the missing shared library (I have no idea which one, or
 where to get it )

 You can use my container, which contains a functioning docker build of
 fossil:
 https://registry.hub.docker.com/u/nijtmans/fossil/

 Regards,
 Jan Nijtmans
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Issue with cloning a repo

[Jacek Cała]

Hi,

I'm running fossil 1.33 in a docker container and found an issue when
cloning my repo. If I run it like:

$ fossil clone http://USERNAME@SERVERNAME/REPONAME repo.fossil

it fails reporting:

getaddrinfo() fails: Name or service not known
Clone done, sent: 0  received: 0  ip:
server returned an error - clone aborted

However, it works when issued with the server IP address rather than its
DNS name:

$ fossil clone http://USERNAME@SERVERIPADDR/REPONAME repo.fossil

Yet something like:

$ ssh SERVERNAME

works perfectly fine. It's not urgent for me because I can work using IP
but I'd appreciate any hints how it may be solved.

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Stable sort on ticket reports

[Jacek Cała]

Hi all,

The current sorting algorithm on the ticket report pages is unstable, which
makes it difficult to sort the report by more than one column. Looking into
the code I found relatively easy fix that would turn the sorting functions
into stable one:

for sortText and sortKey the change is just:

if (aa==bb) return a.rowIndex - b.rowIndex;

for sortNumeric it may be:

if (aa==bb) return a.rowIndex - b.rowIndex;
return aa-bb;

or super precisely:

if (aa-bb  0.01) return a.rowIndex - b.rowIndex;
return aa-bb;

Where eps = 0.01 is an arbitrary small float, which causes that numbers
closer to each other than eps are considered equal.

What do you think?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Ticket submission time in a ticket report

[Jacek Cała]

My bad... I meant 'View Ticket Page' as in 'Admin-Tickets-View Ticket
Page'.
I guess, I cannot call sql directly from TH1, can I?

  Cheers,
  Jacek



2015-01-20 21:55 GMT+00:00 Stephan Beal sgb...@googlemail.com:

 On Tue, Jan 20, 2015 at 10:14 PM, Jacek Cała jacek.c...@gmail.com wrote:

 Is there an easy way to show ticket's submission time? I see tkt_datetime
 which is a special TH1 variable that refers to tkt_mtime field from the
 table. In the table there's 'tkt_ctime' but including that in a report
 shows a double value which is of little use for the end users.


 That's a Julian Day time - simply use strftime in your report to convert
 it, e.g.:

 sqlite select distinct strftime('%Y-%m-%d', mtime) from event order by
 mtime desc limit 3 ;
 2014-12-18
 2014-12-17
 2014-12-16

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
 those who insist on a perfect world, freedom will have to do. -- Bigby Wolf

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Ticket submission time in a ticket report

[Jacek Cała]

Hi all,

Is there an easy way to show ticket's submission time? I see tkt_datetime
which is a special TH1 variable that refers to tkt_mtime field from the
table. In the table there's 'tkt_ctime' but including that in a report
shows a double value which is of little use for the end users.

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Ordering ticket priority/severity

[Jacek Cała]

  Hi,

Below is one of my ticket report pages. I'm not entirely sure it's the best
approach but works fine for me. What it does is two selects. The inner
select classifies status, priority, severity and difficulty so then I can
order them appropriately. The outer select presents the data in human
readable way.

Note, that I added extra difficulty column to prioritize shorter tasks over
longer ones (you can easily remove that). Also, this report shows only
unclosed tickets assigned to the current user, again easy to change.

Hope it helps.

  Cheers,
  Jacek

===
SELECT
  CASE WHEN status IN ('Open','Verified') THEN '#ffeedd'
   WHEN status='Blocked' THEN '#ff'
   WHEN status='Review' THEN '#e8e8e8'
   WHEN status='Fixed' THEN '#cfffbd'
   WHEN status='Tested' THEN '#bdffd6'
   WHEN status='Deferred' THEN '#aabaff'
   ELSE '#b8b8b8' END AS 'bgcolor',
  substr(tkt_uuid,1,10) AS '#',
  priority,
  severity,
  difficulty,
  type,
  status,
  assigned_to,
  subsystem,
  CASE WHEN length(title)  60 THEN substr(title,0,57) || '...'
   ELSE title END AS 'title'
FROM (
  SELECT *,
CASE WHEN status IN ('Open','Verified','Blocked') THEN 0
 WHEN status='Review' THEN 1
 WHEN status='Fixed' THEN 2
 WHEN status='Tested' THEN 3
 WHEN status='Deferred' THEN 4
 ELSE 5 END AS 'st',
CASE WHEN priority='Immediate' THEN 0
 WHEN priority='High' THEN 1
 WHEN priority='Medium' THEN 2
 WHEN priority='Low' THEN 3
 ELSE 4 END AS 'p',
CASE WHEN severity='Critical' THEN 0
 WHEN severity='Severe' THEN 1
 WHEN severity='Important' THEN 2
 WHEN severity='Minor' THEN 3
 ELSE 4 END AS 's',
CASE WHEN difficulty='Very_Easy_(0-15mins)' THEN 0
 WHEN difficulty='Easy_(15min-2hr)' THEN 1
 WHEN difficulty='Medium_(2hr-2days)' THEN 2
 WHEN difficulty='Hard_(2days-2weeks)' THEN 3
 ELSE 4 END AS 'd'
FROM ticket
WHERE status != 'Closed' AND (assigned_to = user() OR assigned_to =
'unassigned' OR assigned_to IS NULL)
ORDER BY st, p, s, d, tkt_mtime)
==

2014-10-12 22:00 GMT+01:00 org.fossil-scm.fossil-us...@io7m.com:

 'Lo.

 Currently, if I do, in a ticket report:

   ORDER BY priority, severity

 I definitely get something ordered by priority and severity, but of
 course the ordering relation for both columns is lexicographical. That
 is, Important  Critical because Critical appears earlier in the
 alphabet.

 That's pretty awful! Is there a recommended way to get a better
 ordering relation without having to mutilate the ticket system too
 much?

 M
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Cloning repo

[Jacek Cała]

Stephan, Andy,

Thanks for the quick action re my issue. I'll test it as soon as I have a
little more time (end of this week?).

  Best,
  Jacek


2014-10-06 16:23 GMT+01:00 Stephan Beal sgb...@googlemail.com:

 On Mon, Oct 6, 2014 at 6:24 AM, Andy Bradford amb-fos...@bradfords.org
 wrote:

 After looking  at it, I  don't think  this introduces any  unwanted side
 effects.


 :-D


 autosync-tries dictates  how  many  times ``autosync''  should
 ...autosync-tries would be honored and one would have to enter the
 password
 for a maximum of 2 * autosync-tries.


 That's what it looked like to me. Potentially annoying but harmless (and
 abortable with a Ctrl-C).



 Maybe  if  we  could  distinguish between  password  failure  and  other
 


 Seems to me to be rare corner case which isn't necessary. Maybe in certain
 setups/uses, but i can't say i'd ever conceived of this problem until
 Jacek (the OP) posted it.


 For the archives, here is what happens when I have autosync-tries set to
 2 and a password failure:
 ...
 Autosync failed.
 continue in spite of sync failure (y/N)? n
 $

 Seems to behave as I would expect.  Any other opinions?


 Agreed. No less surprising result for that case comes to mind.

 But now that you mention autosync retry count... i'm not 100% sure i put
 that ++nErrs in the right place:


 http://www.fossil-scm.org/index.html/info/165cc5c093e6ee36a78de5e01f7049235dbc1b1c?ln=1856-1867

 Could i convince you to give that look?


 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal
 Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
 those who insist on a perfect world, freedom will have to do. -- Bigby Wolf

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Cloning repo

[Jacek Cała]

Hi all,

I've noticed an unexecpected behaviour in fossil when doing a clone. The
issue appears when you try clone with a wrong user name and as the result
an empty repo is created. I'd rather expect an error on the console and
nothing else.

The thing is fully reproducible with the latest windows binaries (see
below, when asked just type any random password). Even more unexpectedly
you can try doing this on http://myfakeu...@www.fossil-scm.org/

I'm not sure why failing to login to fossil-scm still clones the repo or
why failing to my repo creates an empty repo. Is this by design?

  Best,
  Jacek

 fossil clone http://myfakeu...@egenome-fossil.cloudapp.net/e-Genome
repo.fossil
password for MyFakeUser: **
remember password (Y/n)? n
Round-trips: 2   Artifacts sent: 0  received: 0
Error: login failed
password for MyFakeUser: *
remember password (Y/n)? n
Round-trips: 3   Artifacts sent: 0  received: 0
Error: login failed
Round-trips: 3   Artifacts sent: 0  received: 0
Clone finished with 907 bytes sent, 865 bytes received
Rebuilding repository meta-data...
  100.0% complete...
project-id: 0f5ea9d3c8bb48d8de1f1075b62026a6c7538d1e
admin-user: MyFakeUser (password is 6af0d9)
 dir
04/10/2014  06:3958,368 repo.fossil
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] ticket that depends on another ticket

[Jacek Cała]

Hi Paolo,

Below are things which I use, based on various answers from the mailing
list. Have a look at these excerpts and put them in the appropriate places
via Admin/Tickets/Edit or View

Basically, I changed the edit and view ticket pages to add/show blockers.
As said above, it's just for informative purposes, so e.g. you will be able
to close ticket with unclosed blockers. But I use it and still find it
handy. BTW, in the view page I use colors to clearly show ticket status,
without proper support from fossil I don't think you can show that a ticket
is blocked by others.

  Hope it helps,
  Jacek

- Edit ticket page -
th1
  if {![info exists mutype]} {set mutype Wiki}
  if {![info exists icomment]} {set icomment {}}
  if {![info exists username]} {set username $login}
  if {[info exists submit]} {
if {$mutype eq Wiki} {
  set mimetype text/x-fossil-wiki
} elseif {$mutype eq HTML} {
  set mimetype text/html
} elseif {$mutype eq {[links only]}} {
  set mimetype text/x-fossil-plain
} else {
  set mimetype text/plain
}

# Set blockers according to the buffered new_blockers list
set blockers $new_blockers

submit_ticket
set preview 1
  }
/th1

...

trtd class=tktDspLabelVersionnbsp;Foundnbsp;In:/tdtd
input type=text name=foundin size=50 value=$foundin /
/td/tr

tr
td class='tktDspLabel'Blockers:/td
th1
  if {! [info exists new_blockers]} {
set new_blockers $blockers
  }

  if {[info exists addblckrbtn]} {
if {[info exists new_blocker]} {
  # Check whether the added blocker is already in the list
  set add_new_blocker 1
  for {set b 0} {$b  [llength $new_blockers]} {set b [expr {$b + 1}]} {
set to_check [lindex $new_blockers $b]
if {![string compare $new_blocker $to_check]} {
  set add_new_blocker 0
  break
}
  }
  if {$add_new_blocker} {
set new_blockers $new_blockers $new_blocker
  }
}
  } elseif {[info exists delblckrbtn]} {
if {[info exists blocker_list]} {
  # Generate a list of blockers that is clear from the deleted blocker
  set cleared_blockers 
  for {set b 0} {$b  [llength $new_blockers]} {set b [expr {$b + 1}]} {
set to_check [lindex $new_blockers $b]
if {[string compare $blocker_list $to_check]} {
  set cleared_blockers $cleared_blockers $to_check
}
  }
  set new_blockers $cleared_blockers
}
  }

  html input type='hidden' name='new_blockers' value='$new_blockers' /
  if {[llength $new_blockers] == 0} {
enable_output 0
  }
/th1
  tdth1combobox blocker_list $new_blockers 3/th1
  input type=submit name=delblckrbtn value=Del blocker //td
/tr
tr
  td/td

th1enable_output 1/th1
  tdinput type=text name=new_blocker size=20 /
  input type=submit name=addblckrbtn value=Add blocker //td
/tr

trtd colspan=2
  Append Remark with format

...
- End of Edit Ticket page -

- View Ticket page -
...

tr
  td class=tktDspLabelTitle:/td
  td class=tktDspValue colspan=3$title/td
/tr
tr
  td class=tktDspLabelStatus:/td
th1
  if {![string compare $status Verified] ||
  ![string compare $status Open]} {
set color #ff
  } elseif {![string compare $status Review]} {
set color #e8e8e8
  } elseif {![string compare $status Fixed]} {
set color #cfffbd
  } elseif {![string compare $status Tested]} {
set color #bdffd6
  } elseif {![string compare $status Deferred]} {
set color #aabaff
  } else {
set color #b8b8b8
  }
  html td class='tktDspValue' style='background: $color'$status/td
/th1
  td class=tktDspLabelType:/td

...

tr
  td class=tktDspLabelVersionnbsp;Foundnbsp;In:/td
  td valign=top class=tktDspValue$foundin/td
  td class=tktDspLabelAssigned to:/td
  td class=tktDspValue$assigned_to/td
/tr
tr
  td class=tktDspLabelBlockers:/td
  td colspan=3 valign=top class=tktDspValue
th1
   # Thanks to Brian Theado
   #
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg00852.html

   # Loop through the ticket uuids
   for {set x 0} {$x  [llength $blockers]} {set x [expr {$x + 1}]} {
 # Add braces so wiki formatter will make links.  Backslashes
 # hide those braces from interpretation by th1
 wiki \[[lindex $blockers $x]\]
   }
/th1
  /td
/tr

th1
if {[info exists comment]  [string length $comment]10} {
  html {
trtd class=tktDspLabelDescription:/td/tr
trtd colspan=5 class=tktDspValue
  }

...

- End of View Ticket page 


2014-09-30 20:17 GMT+01:00 Ron W ronw.m...@gmail.com:

 On Tue, Sep 30, 2014 at 2:17 PM, Stephan Beal sgb...@googlemail.com
 wrote:

 On Tue, Sep 30, 2014 at 6:43 PM, Paolo Bolzoni 
 paolo.bolzoni.br...@gmail.com wrote:

 I am using fossil for bug tracking in a project where (not my
 decision) we use git for revision control.  I was wondering if
 there is a way to explicitly mark a ticket as children of
 another. So it is clear that the root one must worked on before
 the child one.

 It is possible do 

Re: [fossil-users] ticket that depends on another ticket

[Jacek Cała]

Sorry, forgot to add that for the code to work you need also to add field:
blockers TEXT, to the ticket table (Admin/Tickets/Common).

  Cheers,
  Jacek

2014-10-01 6:26 GMT+01:00 Jacek Cała jacek.c...@gmail.com:

 Hi Paolo,

 Below are things which I use, based on various answers from the mailing
 list. Have a look at these excerpts and put them in the appropriate places
 via Admin/Tickets/Edit or View

 Basically, I changed the edit and view ticket pages to add/show blockers.
 As said above, it's just for informative purposes, so e.g. you will be able
 to close ticket with unclosed blockers. But I use it and still find it
 handy. BTW, in the view page I use colors to clearly show ticket status,
 without proper support from fossil I don't think you can show that a ticket
 is blocked by others.

   Hope it helps,
   Jacek

 - Edit ticket page -
 th1
   if {![info exists mutype]} {set mutype Wiki}
   if {![info exists icomment]} {set icomment {}}
   if {![info exists username]} {set username $login}
   if {[info exists submit]} {
 if {$mutype eq Wiki} {
   set mimetype text/x-fossil-wiki
 } elseif {$mutype eq HTML} {
   set mimetype text/html
 } elseif {$mutype eq {[links only]}} {
   set mimetype text/x-fossil-plain
 } else {
   set mimetype text/plain
 }

 # Set blockers according to the buffered new_blockers list
 set blockers $new_blockers

 submit_ticket
 set preview 1
   }
 /th1

 ...

 trtd class=tktDspLabelVersionnbsp;Foundnbsp;In:/tdtd
 input type=text name=foundin size=50 value=$foundin /
 /td/tr

 tr
 td class='tktDspLabel'Blockers:/td
 th1
   if {! [info exists new_blockers]} {
 set new_blockers $blockers
   }

   if {[info exists addblckrbtn]} {
 if {[info exists new_blocker]} {
   # Check whether the added blocker is already in the list
   set add_new_blocker 1
   for {set b 0} {$b  [llength $new_blockers]} {set b [expr {$b + 1}]}
 {
 set to_check [lindex $new_blockers $b]
 if {![string compare $new_blocker $to_check]} {
   set add_new_blocker 0
   break
 }
   }
   if {$add_new_blocker} {
 set new_blockers $new_blockers $new_blocker
   }
 }
   } elseif {[info exists delblckrbtn]} {
 if {[info exists blocker_list]} {
   # Generate a list of blockers that is clear from the deleted blocker
   set cleared_blockers 
   for {set b 0} {$b  [llength $new_blockers]} {set b [expr {$b + 1}]}
 {
 set to_check [lindex $new_blockers $b]
 if {[string compare $blocker_list $to_check]} {
   set cleared_blockers $cleared_blockers $to_check
 }
   }
   set new_blockers $cleared_blockers
 }
   }

   html input type='hidden' name='new_blockers' value='$new_blockers' /
   if {[llength $new_blockers] == 0} {
 enable_output 0
   }
 /th1
   tdth1combobox blocker_list $new_blockers 3/th1
   input type=submit name=delblckrbtn value=Del blocker //td
 /tr
 tr
   td/td

 th1enable_output 1/th1
   tdinput type=text name=new_blocker size=20 /
   input type=submit name=addblckrbtn value=Add blocker //td
 /tr

 trtd colspan=2
   Append Remark with format

 ...
 - End of Edit Ticket page -

 - View Ticket page -
 ...

 tr
   td class=tktDspLabelTitle:/td
   td class=tktDspValue colspan=3$title/td
 /tr
 tr
   td class=tktDspLabelStatus:/td
 th1
   if {![string compare $status Verified] ||
   ![string compare $status Open]} {
 set color #ff
   } elseif {![string compare $status Review]} {
 set color #e8e8e8
   } elseif {![string compare $status Fixed]} {
 set color #cfffbd
   } elseif {![string compare $status Tested]} {
 set color #bdffd6
   } elseif {![string compare $status Deferred]} {
 set color #aabaff
   } else {
 set color #b8b8b8
   }
   html td class='tktDspValue' style='background: $color'$status/td
 /th1
   td class=tktDspLabelType:/td

 ...

 tr
   td class=tktDspLabelVersionnbsp;Foundnbsp;In:/td
   td valign=top class=tktDspValue$foundin/td
   td class=tktDspLabelAssigned to:/td
   td class=tktDspValue$assigned_to/td
 /tr
 tr
   td class=tktDspLabelBlockers:/td
   td colspan=3 valign=top class=tktDspValue
 th1
# Thanks to Brian Theado
#
 http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg00852.html

# Loop through the ticket uuids
for {set x 0} {$x  [llength $blockers]} {set x [expr {$x + 1}]} {
  # Add braces so wiki formatter will make links.  Backslashes
  # hide those braces from interpretation by th1
  wiki \[[lindex $blockers $x]\]
}
 /th1
   /td
 /tr

 th1
 if {[info exists comment]  [string length $comment]10} {
   html {
 trtd class=tktDspLabelDescription:/td/tr
 trtd colspan=5 class=tktDspValue
   }

 ...

 - End of View Ticket page 


 2014-09-30 20:17 GMT+01:00 Ron W ronw.m...@gmail.com:

 On Tue, Sep 30, 2014 at 2:17 PM, Stephan Beal sgb...@googlemail.com
 wrote:

 On Tue

Re: [fossil-users] feature request: tracking/diffing files across renames

[Jacek Cała]

+1 for this. I stumbled upon that a few times and would really like to see
it's there.

  Cheers,
  Jacek


2013/11/30 j. van den hoff veedeeh...@googlemail.com

 regarding this thread

 http://www.mail-archive.com/fossil-users@lists.fossil-scm.
 org/msg12774.html

 and this more recent one

 http://www.mail-archive.com/fossil-users@lists.fossil-scm.
 org/msg13917.html

 I would like to learn whether this issue is still considered low priority
 by the developers (and also the users).

 over time it has come into my way again and again and I can't imagine I'm
 the only one hit by these problems ...

 currently, missing functionality in this domain seems to me one of the few
 remaining notable shortcomings of `fossil'.
 I would be glad, if some improvements were possible here.

 thanks,

 j.





 --
 Using Opera's revolutionary email client: http://www.opera.com/mail/
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Ticket system -- blockers

[Jacek Cała]

Hi all,

About 4 years ago I wrote about a missing feature -- a way to specify that
a ticket is a blocker of another ticket. There was a useful suggestion from
Brian T...  time passed and recently this feature has become more and more
urgent to me, so I decided to implement it.
For those interested I report changes to the ticket table (below) and view
and edit pages (attached source). A remaining issue is that as there're no
hard db constraints on blockers there seems to be no way to verify that the
blocker to be added is actually a valid ticket uuid. Basically, user can
add any text as a blocker.

Any comments appreciated.

  Best regards,
  Jacek


Changes against Fossil version [d2e07756d9] 2013-02-16 00:04:35
In the ticket table (Admin/Tickets/Table) add an extra column:
CREATE TABLE ticket(
...
  comment TEXT,
  blockers TEXT
);
...
th1
  if {![info exists mutype]} {set mutype {[links only]}}
  if {![info exists icomment]} {set icomment {}}
  if {![info exists username]} {set username $login}
  if {[info exists submit]} {
if {$mutype eq Wiki} {
  set mimetype text/x-fossil-wiki
} elseif {$mutype eq HTML} {
  set mimetype text/html
} elseif {$mutype eq {[links only]}} {
  set mimetype text/x-fossil-plain
} else {
  set mimetype text/plain
}

# Set blockers according to the buffered new_blockers list
set blockers $new_blockers

submit_ticket
set preview 1
  }
/th1
table cellpadding=5
trtd class=tktDspLabelTitle:/tdtd
input type=text name=title value=$title size=60 /
/td/tr

trtd class=tktDspLabelStatus:/tdtd
th1combobox status $status_choices 1/th1
/td/tr

trtd class=tktDspLabelType:/tdtd
th1combobox type $type_choices 1/th1
/td/tr

trtd class=tktDspLabelSeverity:/tdtd
th1combobox severity $severity_choices 1/th1
/td/tr

trtd class=tktDspLabelPriority:/tdtd
th1combobox priority $priority_choices 1/th1
/td/tr

trtd class=tktDspLabelResolution:/tdtd
th1combobox resolution $resolution_choices 1/th1
/td/tr

trtd class=tktDspLabelSubsystem:/tdtd
th1combobox subsystem $subsystem_choices 1/th1
/td/tr

th1enable_output [hascap e]/th1
  trtd class=tktDspLabelContact:/tdtd
  input type=text name=private_contact size=40
   value=$private_contact /
  /td/tr
th1enable_output 1/th1

trtd class=tktDspLabelVersionnbsp;Foundnbsp;In:/tdtd
input type=text name=foundin size=50 value=$foundin /
/td/tr

tr
td class='tktDspLabel'Blockers:/td
th1
  if {! [info exists new_blockers]} {
set new_blockers $blockers
  }

  if {[info exists addblckrbtn]} {
if {[info exists new_blocker]} {
  # Check whether the added blocker is already in the list
  set add_new_blocker 1
  for {set b 0} {$b  [llength $new_blockers]} {set b [expr {$b + 1}]} {
set to_check [lindex $new_blockers $b]
if {![string compare $new_blocker $to_check]} {
  set add_new_blocker 0
  break
}
  }
  if {$add_new_blocker} {
set new_blockers $new_blockers $new_blocker
  }
}
  } elseif {[info exists delblckrbtn]} {
if {[info exists blocker_list]} {
  # Generate a list of blockers that is clear from the deleted blocker
  set cleared_blockers 
  for {set b 0} {$b  [llength $new_blockers]} {set b [expr {$b + 1}]} {
set to_check [lindex $new_blockers $b]
if {[string compare $blocker_list $to_check]} {
  set cleared_blockers $cleared_blockers $to_check
}
  }
  set new_blockers $cleared_blockers
}
  }

  html input type='hidden' name='new_blockers' value='$new_blockers' /
/th1
  tdth1combobox blocker_list $new_blockers 3/th1
  input type=submit name=delblckrbtn value=Del blocker //td
/tr
tr
  td/td
  tdinput type=text name=new_blocker size=20 /
  input type=submit name=addblckrbtn value=Add blocker //td
/tr

trtd colspan=2
  Append Remark with format
  th1combobox mutype {Wiki HTML {Plain Text} {[links only]}} 1/th1
  from
  input type=text name=username value=$username size=30 /:br /
  textarea name=icomment cols=80 rows=15
   wrap=virtual class=wikiedit$icomment/textarea
/td/tr

th1enable_output [info exists preview]/th1
trtd colspan=2
Description Preview:brhr
th1
if {$mutype eq Wiki} {
  wiki $icomment
} elseif {$mutype eq Plain Text} {
  set r [randhex]
  wiki verbatim-$r\n[string trimright $icomment]\n/verbatim-$r
} elseif {$mutype eq {[links only]}} {
  set r [randhex]
  wiki verbatim-$r links\n[string trimright $icomment]/verbatim-$r
} else {
  wiki nowiki\n[string trimright $icomment]\n/nowiki
}
/th1
hr
/td/tr
th1enable_output 1/th1

tr
td align=right
input type=submit name=preview value=Preview /
/td
td align=leftSee how the description will appear after formatting./td
/tr

th1enable_output [info exists preview]/th1
tr
td align=right
input type=submit name=submit value=Submit /
/td
td align=leftApply the changes shown above/td
/tr
th1enable_output 1/th1

tr
td align=right
input type=submit name=cancel value=Cancel /
/td
tdAbandon this edit/td
/tr

/table
table 

Re: [fossil-users] Ticket system -- blockers

[Jacek Cała]

 in the field (possibly without commas, or a mixture). Ignoring the
 complication of having to parse/grok the content (it's a minor
 complication, granted, but parsing text is always at least a slight
 annoyance), there's another problem: DVCS. i edit the field, then you close
 the ticket in your copy before i sync my changes to the blocker list. So
 we've now got a closed ticket with open blockers. i don't see how that
 could be made to work (meaning automatically enforced) 100% reliably in a
 DVCS.


Fair enough, it's just that having indicators that something is blocking my
ticket may still be useful -- at least to me. Clearly, I'd sync my repo
before trying to resolve any blockers but at least I know they exist.

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Random thoughts on Fossil v2

[Jacek Cała]

Hi All,

One more feature that I also miss in the current version is selective
commit. I mean something which allows you to see changes as a numbered list
and then commit selectively e.g. issuing 'fossil commit -range 1-10,15'. It
requires that 'fossil changes' is invoked before commit but that's what
users do I guess (at least me).

I find this feature very useful and it is very common in clients to SVN,
Mercurial, etc. And since fossil has embedded client, I'd really like to
see that as well.

Just to let you know, sometime ago I implemented that for myself as it
wasn't that difficult. It worked really nice, even if you changed file list
between 'fossil changes' and 'fossil commit...' calls by
removing/adding/modifying new files (then it just reported error like: 'run
fossil changes again'). One downside I remember was performance, for larger
commits it took much longer to run 'fossil commit' than 'fossil commit
-range xxx' even if a range was a subset of all changes. This was, however,
my simple, proof of concept implementation...

What do you think?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Random thoughts on Fossil v2

[Jacek Cała]

Hi all,

My 2 cents below regarding ticket numbering:

2013/7/22 Stephan Beal sgb...@googlemail.com


 * built-in persistent integer ticket numbers in addition to the SHA1
 ticket/artifact ID.  The SHA1 hexdigest fragments are too geeky for
 management during the weekly status meeting.


 Stable incremental numbers are literally not possible to solve for DCVS
 systems, which is why the SHA's (geeky/unwieldy as they are) are used.


I wrote some time ago about this as I think you can have a simple,
relatively easy to grasp ticket numbering in DCVS (not integer though). It
involves three simple steps:
- project create initializes internal repo ticket number with '1',
- project clone adds suffix '.1' to the repo ticket number,
- creating a ticket increases the last number after the last dot or the
only number if it is the primary project repository.

Having this you would end up with a tree of ticket numbers like:
'1', '2',...
'1.1', '1.2', ...
'2.1', '2.2', ...

and it would reflect the tree structure of all repositories of a project.

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Random thoughts on Fossil v2

[Jacek Cała]

2013/7/22 Stephan Beal sgb...@googlemail.com

 On Mon, Jul 22, 2013 at 4:47 PM, Jacek Cała jacek.c...@gmail.com wrote:

 - project create initializes internal repo ticket number with '1',
 - project clone adds suffix '.1' to the repo ticket number,


 That would require that cloning change the central repo (because it has to
 assign and store the new number for each clone) and would be open to attack
 by simply cloning the repo in a loop. If i clone it 10 times (and i've
 _certainly_ cloned the main fossil repo at least that many times) then i
 end up with 10 different numbers after the dot.

 Hundreds, if no thousands, of clones of the core fossil repo and tcl repos
 exists. i don't see this approach working for those two trees.

 Or am i missing/misunderstanding some detail?


Sorry for not being precise enough. You don't need to change the central
repo. In fact you don't change any repo at all. Only during cloning you
create a new 'seed' ticket number. Each repository has its own, ticket
number prefix, either '1' if it is created or '...n.n.1' if it is cloned.

Together with this 'seed' each repo has it's last_ticket_number variable
(initalized with 1) which is a simple integer added to the seed and
incremented on the 'create ticket' operation. I was to quick to say about
dots only, so the last_ticket_number is added to the seed with, let say, a
dash. Then, a ticket number is constructed as 'seed-last_ticket_number'.

Cloning creates a repository tree:
1
1.1
1.2
1.3
1.2.1
etc.

whereas creating tickets adds an internal ticket number (independent for
each repo) and so you can have:
1-1, 1-2, 1-3
1.1-1, 1.1-2
1.2.1-1, 1.2.1-2,...

Is this clearer?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fwd: Fossil design error and possible ways to fix it

[Jacek Cała]

Personally, I don't mind if you go for option (1). From the fossil timeline
you mentioned (
http://www.fossil-scm.org/fossil/timeline?c=2012-11-21+16%3A28%3A03) it
seems that it's not a big issue at all.
I believe that all relevant comments can be easily edited by hand for all
those who really need that.

The biggest advantages of (1) is minimal change to code and this means less
work, less errors and smaller codebase.

  Cheers,
  Jacek


2012/11/23 Richard Hipp d...@sqlite.org



 On Fri, Nov 23, 2012 at 5:15 AM, fossil-m...@h-rd.org wrote:

 Hi,

 I think the cleanest solution is to extend the artifact format by adding
 optional mimetype fields to the
 end of C and J cards (solution 3a)

 Together with this let people choose at ticket/comment creation if its
 text (default) or html.

 For the backward compatibility:  Do old fossil builds just ignore the
 additional fields?   Then there is no problem.


 The artifact parser is very strict.  Any extra fields, or even any extra
 whitespace, at the end of a card causes the entire artifact to be rejected.



 This reminds me of another (maybe can of worms) idea:  Why not let users
 add J fields per repository, they could be used to store file permissions
 etc, but are the responsibility of the repository, not the fossil
 executable.





 __**_
 fossil-users mailing list
 fossil-users@lists.fossil-scm.**org fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**
 fossil-usershttp://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Questions about using tag

[Jacek Cała]

2012/11/23 Richard Hipp d...@sqlite.org

 fossil commit -f --tag release --tag version-3.7.15 --bgcolor #d0c0ff'


This hint (and others you mentioned later in your e-mail) is really useful
to know.

IMHO it is much more important to update documentation with such {clever
hints/best practices} than invest time to handle minor issues like the last
one with text/x-fossil-wiki - text/plain.

  Best,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] comparison with Git

[Jacek Cała]

Hi all,

My two cents:

I like phrase *commit jungle* and sometimes would like to revert some
commits or re-commit things a bit different. I also suppose that it
is not that rare when people commit something by mistake or something
which has not been tested enough. On the other hand my gut feeling is
that (apart from what was said before) changing history is just bad
and should be avoided.

Perhaps the tooling you are talking about is just a filtered commit
view. I mean if fossil allowed users to attach a tag (e.g. private)
to commits to say that they aren't visible in the timeline by default,
we could avoid the jungle and also keep exact history by giving users
a full view option where everything is visible (as it is shown
currently).

Also the thing is that some commits tend to be more important than
others (you usually tag somehow like version X.Y). But in this context
it's perhaps better to say that some commits are much less important
than others (e.g. correcting a spelling mistake in the comments). I
think that the filtered view would allow to hide these.

Michal would that be enough for you to match with the git rewriting
option (which I'm not aware of)?

  Cheers,
  Jacek


2012/9/14 Michal Suchanek hramr...@gmail.com:
 On 14 September 2012 15:52, Richard Hipp d...@sqlite.org wrote:


 On Fri, Sep 14, 2012 at 9:35 AM, Michal Suchanek hramr...@gmail.com wrote:


 The thing to which promoters of immutable history are blind is that
 while exact history record of development of particular feature might
 be interesting and educational it is not the primary purpose if VCS.


 The exact preservation of history is considered best practice for
 high-reliability and safety-critical systems.  Fossil, for example, was
 designed to meet the VCS requirements of DO-178B level A.  (Ref:
 http://en.wikipedia.org/wiki/DO-178B)

 You might not think that exact preservation of history is one of the primary
 purposes of VCS, but not every project manager thinks exactly like you.


 I don't think that's a bad goal. The failure I see is inadequate tools
 for working with the resulting commit jungle. And if you were really
 obstinate about that then fossil fails in that it does not record
 *every* change, it requires explicit commits.

 Thanks

 Michal
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] comparison with Git

[Jacek Cała]

2012/9/14 Bill Burdick bill.burd...@gmail.com:

 Sure, you could have named, alternate timelines and just choose which one to
 make the default, each timeline forming a namespace for its branches and
 tags and timelines could inherit from other timelines.  That way you could
 have rabasing without losing history.


Hmmm... being pragmatic, who would like to have many timelines in the
same project? IMHO that would make things quite complicated or at
least unclear. Whereas the 'private' commit tags (which I mentioned
above) would make things easier I believe; easier to implement and
easier to use.

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] comparison with Git

[Jacek Cała]

2012/9/14 Bill Burdick bill.burd...@gmail.com:

 Private commit tags sound a little less versatile than Git rebasing.


As said above, I don't really know how git rebasing works. Could you
shed more light on why it is more versatile than the simple private
tags?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] comparison with Git

[Jacek Cała]

Thanks Bill for the explanation.

I see private tags as the end result of 'squash' rather than 'edit'.
If you have three commits A-B-C and decide to hide B, you will see
A-C. And then diff between C-A will show combined commits B+C against
A.

Regarding 'edit' and 'reorder', while 'edit' could be useful, I see
reordering as asking for troubles. I wonder if anyone uses it with
shared repos?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] comparison with Git

[Jacek Cała]

2012/9/14 Michal Suchanek hramr...@gmail.com:

 so you do a rebase so that your commits can be applied on top of F and
 send then for review:

 A-B-C-D-E-F-X'-Y'-Z'

 If there are no conflicts between your changes and upstream this is
 fine, otherwise you have to resolve them somehow, and upstream then
 does not have to. They get nice linear history.

I don't understand. Without rebase you just merge the other branch
(D-E-F) to your cloned and updated repo (X-Y-Z), resolve any conflicts
and end up in the same point, ok with one more commit which is the
merge of F to Z.

 This leaves behind a hidden stump with the original X Y and Z commits
 in git. In fossil the stump would remain and you would have to go out
 of your way to hide it or not upload it during push.

Is a short branch in the timeline such a bad thing really?

 Also if Z is really a fix for a bug in X which is not upstream yet you
 might want to do an edit - swap Y and Z and squash X and Z so that the
 upstream reviewer has easier job reviewing fewer patches.

 A-B-C-D-E-F-X'Z'-Y'

That might be useful. But what if someone was tempted to do this for a
fix to a patch that was done 100 commits earlier... Might become
tricky I suppose.

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] A counter in the ticket name

[Jacek Cała]

Alternatively, if prefixes (or better suffixes) are attached when
cloning, you wouldn't need that. Say my master/primary repo has prefix
'1', so when I clone from it my repo would get from the master 1.1 for
the first time and 1.N for the n-th time. When someone clones from my
1.1 repo -- exactly the same 1.1.N. I believe the prefixes wouldn't
grow that much because most of the time users would clone from the
master/primary repo.

  Cheers,
  Jacek

2012/7/4 Richard Hipp d...@sqlite.org:


 On Wed, Jul 4, 2012 at 3:09 AM, Ron Wilson ronw.m...@gmail.com wrote:

 On Fri, Jun 15, 2012 at 7:06 AM, Jacek Cała jacek.c...@gmail.com wrote:
  Right. I tend to forget about the distributed aspect of fossil as I
  mostly work with the centralized setup.

 On the other hand, you could give each instance its own prefix, then
 all the ticket numbers would be unique.


 You'd still need a centralized authority to assign the prefixes.



 This is a lot of hastle, but
 sometimes these hastles are necessary to get management to agree. FYI,
 there are still managers who will go to the hastle of maintaining
 issues with a spreadsheet. This is simple and easy for them to
 understand despite all the manual work of keeping the spreadsheet
 organized.
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

[Jacek Cała]

Hello Richard,

I was going to write to you about reappearance of the 'malformed
manifest' problem but found that you had checked in a fix to the
previous bug fix. Now, I can confirm that the last fix [5f3a0681a0]
works fine for me.

  Thank you,
  Jacek


2012/6/29 Richard Hipp d...@sqlite.org:


 On Fri, Jun 29, 2012 at 8:36 AM, Jacek Cała jacek.c...@gmail.com wrote:

 Thank you for the prompt action. Please keep me/the list informed
 about the patch.


 Please try the latest trunk version of Fossil.  I believe it has fixed your
 issue and should be working for you now.



 Maybe it is also worth considering the case when a file has just been
 added to the repo (no commit) and then mv is issued from a MISSING to
 the ADDED file. I wrote about it a couple of days ago:

 http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg08936.html

  Best regards,
  Jacek

 2012/6/29 Richard Hipp d...@sqlite.org:
 
 
  On Fri, Jun 29, 2012 at 5:33 AM, Jacek Cała jacek.c...@gmail.com
  wrote:
 
   Hi,
 
  I've been doing some code maintenance (lots of deletes, renames, adds)
  and now cannot do commit. Every commit attempt causes:
 
   fossil.exe: manifest file (1816) is malformed.
 
  What does this mean? Is there any chance to fix the repo? My fossil
  version is 1.22.
 
 
  I have traced this problem to a bug in Fossil's manifest generator which
  causes rows of the manifest to be created out of order if you have done
  a
  fossil mv but then do a fossil commit FILENAME... where the renamed
  files are not being committed.  Working on a fix now...
 
 
 
 
 
   Jacek
 
  ___
  fossil-users mailing list
  fossil-users@lists.fossil-scm.org
  http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
 
 
 
  --
  D. Richard Hipp
  d...@sqlite.org
 
  ___
  fossil-users mailing list
  fossil-users@lists.fossil-scm.org
  http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Turning off change tracking for certain files

[Jacek Cała]

  Hi All,

I've got in my repo a small number of files that are changing but
these changes are not meant to be send to the repo (are kind of
user-specific). The files are needed in the repo but only in their
initial or some specific version. Is there any way to turn off change
tracking for some files? To be clearer, when doing 'fossil open
myrepo' I'd like these files to appear in the filesystem but when
doing 'fossil chan' I'd like them to not appear, maybe only when
MISSING.

I would expect this to work similar to 'fossil settings ignore-glob'
w.r.t. 'fossil extra'.


  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Turning off change tracking for certain files

[Jacek Cała]

Hi Stephan,

I think it is an scm-level problem, at least for me ;-)

The thing is that either I'll commit these file every time they change
(which makes a bit of mess in the repo) or I need to do a selective
commit which omits these files (which after a tens of commits become a
bit annoying).

  Cheers,
  Jacek

2012/7/2 Stephan Beal sgb...@googlemail.com:
 Hi! No, there us no such mechanism in fossil. I sometimes have similar
 problems with makefiles and config files, but i have never considered that
 to be an scm-level problem (maybe it is?).

 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal

 On Jul 2, 2012 11:24 AM, Jacek Cała jacek.c...@gmail.com wrote:

   Hi All,

 I've got in my repo a small number of files that are changing but
 these changes are not meant to be send to the repo (are kind of
 user-specific). The files are needed in the repo but only in their
 initial or some specific version. Is there any way to turn off change
 tracking for some files? To be clearer, when doing 'fossil open
 myrepo' I'd like these files to appear in the filesystem but when
 doing 'fossil chan' I'd like them to not appear, maybe only when
 MISSING.

 I would expect this to work similar to 'fossil settings ignore-glob'
 w.r.t. 'fossil extra'.


   Cheers,
   Jacek
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Turning off change tracking for certain files

[Jacek Cała]

This is exactly how I would expect it to work. And I like the '--all'
option, too.

The only thing is if anything better than a list like 'ignore-glob'
can be proposed. In my case it's just a few files, so such a list
would be enough. However, I can imagine that someone has a large repo
and needs to set no-autocommit to more than 10 files. Then maintaining
an 'ignore-glob'-like list may become a pain.

  Cheers,
  Jacek

2012/7/2 Richard Hipp d...@sqlite.org:
 I am willing to *consider* some option that says do not commit these files,
 even if they change, unless that are specifically named on the
 command-line.  I think this would be easy to implement by messing with the
 is_selected()/if_selected() function.

 So, to use Stephan's example, if you marked Makefile as no-autocommit, and
 there were changes to both Makefile and to file1.txt, fossil commit would
 only check-in the changes on file1.txt.  But fossil commit Makefile *.txt
 would check-in changes to both file.  Probably there should be another
 command-line option such as fossil commit --all that also picks up
 Makefile.  The changes command should show the changes to Makefile, but
 indicate that they are not checked in by default.  The check-in comment
 prompt string should indicate clearly that Makefile is omitted from the
 check-in because of the setting and it was not specified on the
 command-line.

 I don't think any changes are needed to update or merge or stash.  fossil
 revert is an interesting case - does it revert Makefile to the default, or
 doesn't it?  Maybe fossil revert Makefile or fossil revert --all is
 required?

 Correction:  I think fossil changes should only show Makefile if you give
 it an option like --all.  Otherwise, fossil all changes (whose purpose
 it to show check-outs with any changes that you have forgotten to check-in)
 would give false hits for repos with only Makefile-like changes.




 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Turning off change tracking for certain files

[Jacek Cała]

2012/7/2 Stephan Beal sgb...@googlemail.com:
 On Mon, Jul 2, 2012 at 2:49 PM, Jacek Cała jacek.c...@gmail.com wrote:

 would be enough. However, I can imagine that someone has a large repo
 and needs to set no-autocommit to more than 10 files. Then maintaining
 an 'ignore-glob'-like list may become a pain.


 fossil/sqlite has routines for globbing, so it wouldn't be too painful to do
 things like:

 fossil remember-local 'foo.*'

Fine for me!

  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Turning off change tracking for certain files

[Jacek Cała]

One more thought. Perhaps, there's no need for a separate ignore list
but just a bit different semantics of the existing 'ignore-glob'.
Couldn't it just be that when a file (a set of files '*.whatever') is
in the ignore-glob it behaves exactly like Richard suggested. From a
user perspective that would be simpler -- just one list which means
ignore yet not prevent from being added.

  Cheers,
  Jacek

2012/7/2 Richard Hipp d...@sqlite.org:


 On Mon, Jul 2, 2012 at 7:56 AM, Stephan Beal sgb...@googlemail.com wrote:

 On Mon, Jul 2, 2012 at 1:44 PM, Stephan Beal sgb...@googlemail.com
 wrote:

 i'm not personally convinced that an ignore list would completely solve
 the problem (i think that just might lead to more confusion (i changed the
 file, why isn't it showing as changed?) and corresponding bug reports). But
 it might be a solution or part of a solution. Can you elaborate on how you
 imagine such a feature behaving?


 Maybe we could have a local list, similar to ignore-glob, like:

 fossil forget-local ...list...of...files...
 fossil remember-local ...list...of...files... (undoes the forget)

 Forgotten files would be excluded from commits unless they are
 explicitly named on the command-line (as opposed to being in a directory
 which was passed on the comment line). Fossil status should probably show
 them as changed, in any case.

 But what happens if the remote is updated? Do those files participate in
 merging (i suspect they should)? Are there other corner cases here?


 I am willing to *consider* some option that says do not commit these files,
 even if they change, unless that are specifically named on the
 command-line.  I think this would be easy to implement by messing with the
 is_selected()/if_selected() function.

 So, to use Stephan's example, if you marked Makefile as no-autocommit, and
 there were changes to both Makefile and to file1.txt, fossil commit would
 only check-in the changes on file1.txt.  But fossil commit Makefile *.txt
 would check-in changes to both file.  Probably there should be another
 command-line option such as fossil commit --all that also picks up
 Makefile.  The changes command should show the changes to Makefile, but
 indicate that they are not checked in by default.  The check-in comment
 prompt string should indicate clearly that Makefile is omitted from the
 check-in because of the setting and it was not specified on the
 command-line.

 I don't think any changes are needed to update or merge or stash.  fossil
 revert is an interesting case - does it revert Makefile to the default, or
 doesn't it?  Maybe fossil revert Makefile or fossil revert --all is
 required?

 Correction:  I think fossil changes should only show Makefile if you give
 it an option like --all.  Otherwise, fossil all changes (whose purpose
 it to show check-outs with any changes that you have forgotten to check-in)
 would give false hits for repos with only Makefile-like changes.




 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Turning off change tracking for certain files

[Jacek Cała]

2012/7/2 Stephan Beal sgb...@googlemail.com:
 On Mon, Jul 2, 2012 at 3:04 PM, Jacek Cała jacek.c...@gmail.com wrote:

 Couldn't it just be that when a file (a set of files '*.whatever') is
 in the ignore-glob it behaves exactly like Richard suggested. From a
 user perspective that would be simpler -- just one list which means
 ignore yet not prevent from being added.


 How could the ignore code differentiate between truly ignored files and
 those which are partially ignored?

Is there any difference except from being in the repo. I'd say,
truly ignored files are not in the repo at all, while partially
ignored happen to be although the scm just ignores their local
counterparts. Am I missing something?

  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Turning off change tracking for certain files

[Jacek Cała]

If it happens I have some spare time, I'll look on the
{is/if}_selected and will report on any progress.

  Cheers,
  Jacek


2012/7/2 Stephan Beal sgb...@googlemail.com:
 On Mon, Jul 2, 2012 at 3:09 PM, Jacek Cała jacek.c...@gmail.com wrote:

 Is there any difference except from being in the repo. I'd say,
 truly ignored files are not in the repo at all, while partially
 ignored happen to be although the scm just ignores their local
 counterparts. Am I missing something?


 That's my point: fossil has to completely ignore one set and only deal with
 the other set in certain cases. In order to that, it has to be able to
 differentiate between the two sets of files. It can't do that if they're all
 in the ignore-glob (which has very specific semantics which users rely
 upon).

 In any case, Richard indicated that it shouldn't be too hard to implement
 using existing functionality. i can't personally commit to implementing it
 in the near future, but it's something i'd like to see at least
 experimentally implemented. In hindsight, i can't believe this feature
 suggestion has never come up before :/.

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] cannot commit 'manifest file (1816) is malformed'

[Jacek Cała]

  Hi,

I've been doing some code maintenance (lots of deletes, renames, adds)
and now cannot do commit. Every commit attempt causes:

 fossil.exe: manifest file (1816) is malformed.

What does this mean? Is there any chance to fix the repo? My fossil
version is 1.22.

  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

[Jacek Cała]

d:\...\MainSolutionfossil test-agg-cksum
disk: 9b15edd8f59e6d06f24779627eb5d751
archive:  ef042e223a29de7097b5bac505295812
manifest: 064345fe886bffeb23131fcc0ac5a5d5
recorded: 064345fe886bffeb23131fcc0ac5a5d5

Hardly readable for me :-) but no errors.

  Cheers,
  Jacek

2012/6/29 Stephan Beal sgb...@googlemail.com:
 On Fri, Jun 29, 2012 at 11:33 AM, Jacek Cała jacek.c...@gmail.com wrote:

  fossil.exe: manifest file (1816) is malformed.

 What does this mean? Is there any chance to fix the repo? My fossil
 version is 1.22.


 That's a new one. :/

 Can you please try:

 fossil test-agg-cksum

 just to make sure that the basic checks for that function work?

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

[Jacek Cała]

2012/6/29 Richard Hipp d...@sqlite.org:

 It means there is a bug in Fossil.  ...

 Note that the changes to the repository happen inside a transaction.  ...
 ... This is one of the big advantages of using a transactional database engine
 as the repository, rather than a pile-of-files as in other VCSes - bugs are
 annoying but do not cause repository corruption.


And this is also the thing why I like fossil even more!

  Thanks,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

[Jacek Cała]

Thank you for the prompt action. Please keep me/the list informed
about the patch.

Maybe it is also worth considering the case when a file has just been
added to the repo (no commit) and then mv is issued from a MISSING to
the ADDED file. I wrote about it a couple of days ago:
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg08936.html

  Best regards,
  Jacek

2012/6/29 Richard Hipp d...@sqlite.org:


 On Fri, Jun 29, 2012 at 5:33 AM, Jacek Cała jacek.c...@gmail.com wrote:

  Hi,

 I've been doing some code maintenance (lots of deletes, renames, adds)
 and now cannot do commit. Every commit attempt causes:

  fossil.exe: manifest file (1816) is malformed.

 What does this mean? Is there any chance to fix the repo? My fossil
 version is 1.22.


 I have traced this problem to a bug in Fossil's manifest generator which
 causes rows of the manifest to be created out of order if you have done a
 fossil mv but then do a fossil commit FILENAME... where the renamed
 files are not being committed.  Working on a fix now...





  Jacek

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] cannot commit 'manifest file (1816) is malformed'

[Jacek Cała]

Yes, the commit went fine. Thank you again!

  Jacek

2012/6/29 Richard Hipp d...@sqlite.org:


 On Fri, Jun 29, 2012 at 8:36 AM, Jacek Cała jacek.c...@gmail.com wrote:

 Thank you for the prompt action. Please keep me/the list informed
 about the patch.


 Please try the latest trunk version of Fossil.  I believe it has fixed your
 issue and should be working for you now.



 Maybe it is also worth considering the case when a file has just been
 added to the repo (no commit) and then mv is issued from a MISSING to
 the ADDED file. I wrote about it a couple of days ago:

 http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg08936.html

  Best regards,
  Jacek

 2012/6/29 Richard Hipp d...@sqlite.org:
 
 
  On Fri, Jun 29, 2012 at 5:33 AM, Jacek Cała jacek.c...@gmail.com
  wrote:
 
   Hi,
 
  I've been doing some code maintenance (lots of deletes, renames, adds)
  and now cannot do commit. Every commit attempt causes:
 
   fossil.exe: manifest file (1816) is malformed.
 
  What does this mean? Is there any chance to fix the repo? My fossil
  version is 1.22.
 
 
  I have traced this problem to a bug in Fossil's manifest generator which
  causes rows of the manifest to be created out of order if you have done
  a
  fossil mv but then do a fossil commit FILENAME... where the renamed
  files are not being committed.  Working on a fix now...
 
 
 
 
 
   Jacek
 
  ___
  fossil-users mailing list
  fossil-users@lists.fossil-scm.org
  http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
 
 
 
  --
  D. Richard Hipp
  d...@sqlite.org
 
  ___
  fossil-users mailing list
  fossil-users@lists.fossil-scm.org
  http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] mv after add breaks

[Jacek Cała]

Hi All,

I moved a file (say file1.txt) from one dir to another and, in the
same time, changed its name (say, to dir1\file2.txt); it was
relatively long so I forgot about the move. Then I tapped (all names
changed for clarity):

fossil extra
dir1/file2.txt

fossil add dir1
ADDED dir1/file2.txt

fossil chan
MISSING file1.txt
ADDED dir1/file2.txt

At this moment I realized that file1.txt was actually changed to
dir1/file2.txt, so I happily issued:

fossil mv file1.txt dir1/file2.txt
RENAME file1.txt dir1/file2.txt
d:\usr\local\fossil\fossil.exe: SQLITE_CONSTRAINT: abort at 42 in
[UPDATE vfile SET pathname='dir1/file2.txt' WHERE pathname='... path
name cut in the middle'
d:\usr\local\fossil\fossil.exe: columns pathname, vid are not unique
UPDATE vfile SET pathname='dir1/file2.txt' WHERE pathname='file1.txt'
AND vid=1749

If you have recently updated you fossil executable, you might
need to run fossil all rebuild to bring teh repository
schemas up to date.



... Then less happily I did:
fossil del dir1/file2.txt
DELETED dir1/file2.txt

and followed my usual way in such cases:
fossil mv file1.txt dir1/file2.txt
RENAME file1.txt dir1/file2.txt

which went fine.

I may be wrong but think that moves of an added file should be
possible, shouldn't they?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] A counter in the ticket name

[Jacek Cała]

  Hi All,

I thought about implementing a counter to help with ticket
identification for users (IMO, UUIDs are a bit obscure and have no
order).
My idea was to include an integer value into some table in the repo,
read it with TH1 before creation of a new ticket, and increment and
store it in the table just after the ticket creation.

Could anyone more acquainted with the fossil code suggest if this idea
is right. Am I able to do it only by editing the Admin/Tickets/...
pages or some source code changes are required?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] A counter in the ticket name

[Jacek Cała]

Right. I tend to forget about the distributed aspect of fossil as I
mostly work with the centralized setup.

Thanks for quick answer before I started :-) !

  Cheers,
  Jacek

2012/6/15 Stephan Beal sgb...@googlemail.com:
 On Fri, Jun 15, 2012 at 12:28 PM, Jacek Cała jacek.c...@gmail.com wrote:

 I thought about implementing a counter to help with ticket
 identification for users (IMO, UUIDs are a bit obscure and have no
 order).


 A counter cannot work in a distributed system, which is why _all_ of them
 use UUIDs in some form or another.

 What happens when i create a ticket on my machine and you create one on
 yours, and then we both push? Who's ticket #1 is correct?

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/
 http://gplus.to/sgbeal


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil vs. Windows

[Jacek Cała]

2012/6/13 Rene renew...@xs4all.nl:
 On 2012-06-12 00:36, Mike Meyer wrote:

 My boss just sent me mail that said, and I quote:

   Fossil sucks and is actually not compatible with Windows


 Mike,

 ...
 Better sit down with him and ask him what the problem is, maybe first a few
 pints of strong lager.
 ...

 It is not a technical issue.
 --

Fully agree!

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil vs. Windows

[Jacek Cała]

  Hi Mike,

See the sample session below. All works as you would expect.
Obviously, it is a trivial example and I don't mean there are no bugs
in fossil. It's just I've never encountered any w.r.t. spaces in
file/dir names.

  Cheers,
  Jacek

d:\tmp\space dirfossil init d:\cala\data\fossil test repo\space repo.fossil
project-id: f70c97386adaa6bec27c0dcc527c10d8dd402a88
server-id:  3f07ec4cf14b58a30a3ccdc3f0d5471458b6a92b
admin-user: Jacek (initial password is f0dc4f)

d:\tmp\space dirfossil open d:\cala\data\fossil test repo\space repo.fossil

d:\tmp\space dirfossil add new file.txt
ADDED  new file.txt

d:\tmp\space dirfossil chan
  1 ADDED  new file.txt

d:\tmp\space dirfossil commit -m new file added
New_Version: dfb176fe997a79ea339f5a6245bc779f5da06d37

d:\tmp\space dirfossil time
=== 2012-06-12 ===
17:04:29 [dfb176fe99] *CURRENT* new file added (user: Jacek tags: trunk)
17:03:51 [6c6f984764] initial empty check-in (user: Jacek tags: trunk)

d:\tmp\space dirfossil close

d:\tmp\space dirrm new file.txt

d:\tmp\space dirfossil open d:\cala\data\fossil test repo\space repo.fossil
new file.txt
project-name: unnamed
repository:   d:\cala\data\fossil test repo\space repo.fossil
local-root:   d:/tmp/space dir/
user-home:C:/Users/Jacek/AppData/Local
project-code: f70c97386adaa6bec27c0dcc527c10d8dd402a88
checkout: dfb176fe997a79ea339f5a6245bc779f5da06d37 2012-06-12 17:04:29 UTC
parent:   6c6f9847648b79df53dc38538873f54b0c3212b3 2012-06-12 17:03:51 UTC
tags: trunk
comment:  new file added (user: Jacek)

d:\tmp\space dirdir
 Volume in drive D is Data
 Volume Serial Number is 1ADA-2296

 Directory of d:\tmp\space dir

12/06/2012  18:04DIR  .
12/06/2012  18:04DIR  ..
12/06/2012  18:04 6 new file.txt
12/06/2012  18:04 7,168 _FOSSIL_
   2 File(s)  7,174 bytes
   2 Dir(s)   7,288,463,360 bytes free


2012/6/12 Mike Meyer m...@mired.org:
 On Tue, 12 Jun 2012 00:15:08 +0100
 Jacek Cała jacek.c...@gmail.com wrote:

 Hi,

 Could you please be a bit more specific about what errors exactly you
 have experienced.

 I wish I could. It's my boss that's having problems, and I've already
 sent the full report to him. I'm now pursuing this on my own time.

 I've been using fossil on Windows (Vista 32-bit and 7 64-bit) for more
 than 3 years now and haven't ever experienced any problems with spaces
 in dirs or file names;

 How about the path to the repository? He can't get fossil open to
 work (or at least, that's the last report I had).

     Thanks,
     mike
 --
 Mike Meyer m...@mired.org              http://www.mired.org/
 Independent Software developer/SCM consultant, email for more information.

 O ascii ribbon campaign - stop html mail - www.asciiribbon.org
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil vs. Windows

[Jacek Cała]

Hi,

Could you please be a bit more specific about what errors exactly you
have experienced.
I've been using fossil on Windows (Vista 32-bit and 7 64-bit) for more
than 3 years now and haven't ever experienced any problems with spaces
in dirs or file names;

Below is an excerpt from the listing of one of my repos that I work
intensively on. My current fossil ver says:

 fossil version
This is fossil version 1.22 [5dd5d39e7c] 2012-03-19 12:45:47 UTC

But, as said, I've been using much, much older versions, too.

 fossil ls
...
MonitoringCore/Installers.cs
MonitoringCore/Lib/Castle.Windsor-2.5.3/ASL - Apache Software
Foundation License.txt
MonitoringCore/Lib/Castle.Windsor-2.5.3/BreakingChanges.txt
...
eSC-blocks/Execute Multiple Workflows with Properties/classes/MyService.class
eSC-blocks/Execute Multiple Workflows with Properties/dependencies.xml

  Cheers,
  Jacek


2012/6/11 Mike Meyer m...@mired.org:
 My boss just sent me mail that said, and I quote:

   Fossil sucks and is actually not compatible with Windows

 I'm pretty sure I've seen people here who use it no Windows, and
 there's a Windows distribution, which makes me think he's wrong.

 His problem is that he has lots of spaces in his directory and file
 names, and we (Windows is a third-line gaming platform for me, but I
 try...) couldn't figure out how to get such passed to fossil as file
 names, instead of broken up by command.com or whatever does that job
 these days. Quoting again:

    If I try adding parentheses or quotes then the ignorant
    application bombs out.

 So, anyone got advice on this? Maybe a GUI that works with the fossil
 Windows binary from fossil.org?

        Thanks,
        mike
 --
 Mike Meyer m...@mired.org              http://www.mired.org/
 Independent Software developer/SCM consultant, email for more information.

 O ascii ribbon campaign - stop html mail - www.asciiribbon.org
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Fossil vs. Windows

[Jacek Cała]

Hi again,

Sorry for not answering your question in my previous post... I'm a bit
sleepy (it's about 1am my time).

Try double quotes. Just tested with no errors:

 fossil add new file.txt
ADDED  new file.txt

 fossil chan
ADDED  new file.txt

 fossil commit -m new file added...
New_Version: 4023b409f054b270412af3302e79ad20a67de5c0

However, I think you usually don't need to specify file names by hand.
It's enough to issue
'fossil add *' or 'fossil add a_dir' or 'fossil add a_dir\b dir' and
fossil will do the job you.

  Jacek

2012/6/11 Mike Meyer m...@mired.org:
 My boss just sent me mail that said, and I quote:

   Fossil sucks and is actually not compatible with Windows

 I'm pretty sure I've seen people here who use it no Windows, and
 there's a Windows distribution, which makes me think he's wrong.

 His problem is that he has lots of spaces in his directory and file
 names, and we (Windows is a third-line gaming platform for me, but I
 try...) couldn't figure out how to get such passed to fossil as file
 names, instead of broken up by command.com or whatever does that job
 these days. Quoting again:

    If I try adding parentheses or quotes then the ignorant
    application bombs out.

 So, anyone got advice on this? Maybe a GUI that works with the fossil
 Windows binary from fossil.org?

        Thanks,
        mike
 --
 Mike Meyer m...@mired.org              http://www.mired.org/
 Independent Software developer/SCM consultant, email for more information.

 O ascii ribbon campaign - stop html mail - www.asciiribbon.org
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Building portable fossil

[Jacek Cała]

Looks like the binary built with --with-openssl=none --static on my
fedora works on ubuntu (despite the warnings about static linking
against glibc).

Thanks all for help.

  Cheers,
  Jacek

2012/6/2 Jacek Cała jacek.c...@gmail.com:
 Thank you all for your suggestions!

 Seems that it is not that obvious at all... I'll try the other way: to
 compile on fedora and then run on ubuntu.

 BTW, the details are:

 *** Ubuntu 12.04 32-bit with libc.so.6 (libc6, OS ABI: Linux 2.6.24)
 GNU C Library (Ubuntu EGLIBC 2.15-0ubuntu10) stable release version
 2.15, by Roland McGrath et al.
 Copyright (C) 2012 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.
 There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
 PARTICULAR PURPOSE.
 Compiled by GNU CC version 4.6.3.
 Compiled on a Linux 3.2.14 system on 2012-04-19.
 Available extensions:
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
 libc ABIs: UNIQUE IFUNC

 *** Fedora 7 with libc.so.6 (libc6, OS ABI: Linux 2.6.9)
 GNU C Library stable release version 2.6, by Roland McGrath et al.
 Copyright (C) 2007 Free Software Foundation, Inc.
 This is free software; see the source for copying conditions.
 There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
 PARTICULAR PURPOSE.
 Compiled by GNU CC version 4.1.2 20070502 (Red Hat 4.1.2-12).
 Compiled on a Linux 2.6.9 system on 2007-07-08.
 Available extensions:
        The C stubs add-on version 2.1.2.
        crypt add-on version 2.1 by Michael Glad and others
        GNU Libidn by Simon Josefsson
        Native POSIX Threads Library by Ulrich Drepper et al
        BIND-8.2.3-T5B
        RT using linux kernel aio


 2012/6/2 Rene renew...@xs4all.nl:
 On 2012-06-02 03:16, Jacek Cała wrote:

 Thank you for the hint but it doesn't help. This time I get with my
 binary:

 FATAL: kernel too old
 Segmentation fault

 while the official one works fine.

  Jacek

 2012/6/2 Richard Hipp d...@sqlite.org:



 On Fri, Jun 1, 2012 at 8:34 PM, Jacek Cała jacek.c...@gmail.com wrote:


  Hi,

 I built fossil on Ubuntu with a standard configuration (./configure;
 make) but when moved and ran the binary on fedora it complained that
 there's no libssl.so.1.0.0. Indeed, on the fedora is no
 libssl.so.1.0.0 but libssl.so.

 When I turned off the ssl support (./configure --with-ssl=none; make)
 and rebuilt, it complained on fedora about missing versions of glibc:

  /lib/libc.so.6: version `GLIBC_2.7' not found
  /lib/libc.so.6: version `GLIBC_2.15' not found



 Try:

 ./configure --with-ssl=none --static; make

 Then run strip fossil when done.



 What is the trick to build a portable binary like the one officially
 available on the website?

 Also, I noticed that my binary is over 3.5MB whereas the official one
 takes only 1.6MB. Any hints appreciated.

  Cheers,
  Jacek
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org

 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users





 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org

 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org

 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users



 ./configure --with-openssl=none --static; make
                   
 then it says:

 bld/shell.o: In function `find_home_dir':
 /home/renez/src/fossil/./src/shell.c:2700: warning: Using 'getpwuid' in
 statically linked applications requires at runtime the shared libraries from
 the glibc version used for linking
 bld/http_socket.o: In function `socket_open':
 /home/renez/src/fossil/./src/http_socket.c:151: warning: Using
 'gethostbyname' in statically linked applications requires at runtime the
 shared libraries from the glibc version used for linking

 libnsl and libc are necessary to run this executable.
 That is probably also true for the fossil executable  from the website.

 http://www.kernel.org/pub/software/libs/glibc/hjl/compat/ tells how to
 compile for  a version of glibc


 I think we need to look at environments to see what causes the differences
 Yours are
       1) Ubuntu version ?? libc  ??
       2) Fedora version ?? libc  ??
 Mine
       1) Arch linux latest(64 bits that might add something to the size)
          libc (just type /lib/libc.so.6  and press enter)
          GNU C Library stable release version 2.15, by Roland McGrath et al
          Compiled by GNU CC version 4.7.0 20120324 (prerelease).
          Compiled on a Linux 3.3.0 system on 2012-03-29.
          Available extensions:
     crypt add-on version 2.1 by Michael Glad and others
     GNU Libidn

[fossil-users] Building portable fossil

[Jacek Cała]

  Hi,

I built fossil on Ubuntu with a standard configuration (./configure;
make) but when moved and ran the binary on fedora it complained that
there's no libssl.so.1.0.0. Indeed, on the fedora is no
libssl.so.1.0.0 but libssl.so.

When I turned off the ssl support (./configure --with-ssl=none; make)
and rebuilt, it complained on fedora about missing versions of glibc:

  /lib/libc.so.6: version `GLIBC_2.7' not found
  /lib/libc.so.6: version `GLIBC_2.15' not found

What is the trick to build a portable binary like the one officially
available on the website?

Also, I noticed that my binary is over 3.5MB whereas the official one
takes only 1.6MB. Any hints appreciated.

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Building portable fossil

[Jacek Cała]

Thank you for the hint but it doesn't help. This time I get with my binary:

FATAL: kernel too old
Segmentation fault

while the official one works fine.

  Jacek

2012/6/2 Richard Hipp d...@sqlite.org:


 On Fri, Jun 1, 2012 at 8:34 PM, Jacek Cała jacek.c...@gmail.com wrote:

  Hi,

 I built fossil on Ubuntu with a standard configuration (./configure;
 make) but when moved and ran the binary on fedora it complained that
 there's no libssl.so.1.0.0. Indeed, on the fedora is no
 libssl.so.1.0.0 but libssl.so.

 When I turned off the ssl support (./configure --with-ssl=none; make)
 and rebuilt, it complained on fedora about missing versions of glibc:

  /lib/libc.so.6: version `GLIBC_2.7' not found
  /lib/libc.so.6: version `GLIBC_2.15' not found


 Try:

 ./configure --with-ssl=none --static; make

 Then run strip fossil when done.



 What is the trick to build a portable binary like the one officially
 available on the website?

 Also, I noticed that my binary is over 3.5MB whereas the official one
 takes only 1.6MB. Any hints appreciated.

  Cheers,
  Jacek
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Example ticket reports

[Jacek Cała]

  Hi Chen,

Below are two which I tend to use for all my own projects. I'm not
sure if they are the best SQL ever but work fine for my purposes.
All but closed tickets gives you a view sorted by status, priority,
severity and submission time. Counters may be used for auditing
purposes to show the progress and status of the project. Hope it
helps.

  Cheers,
  Jacek

*** All but closed ***

SELECT
  CASE WHEN status IN ('Open','Verified') THEN '#f2dcdc'
   WHEN status='Blocked' THEN '#ff'
   WHEN status='Review' THEN '#e8e8e8'
   WHEN status='Fixed' THEN '#cfe8bd'
   WHEN status='Tested' THEN '#bde5d6'
   WHEN status='Deferred' THEN '#cacae5'
   ELSE '#c8c8c8' END AS 'bgcolor',
  substr(tkt_uuid,1,10) AS '#',
  priority,
  severity,
  type,
  status,
  subsystem,
  CASE WHEN length(title)  60 THEN substr(title,0,57) || '...'
   ELSE title END AS 'title'
FROM (
  SELECT *,
CASE WHEN status IN ('Open','Verified','Blocked') THEN 0
 WHEN status='Review' THEN 1
 WHEN status='Fixed' THEN 2
 WHEN status='Tested' THEN 3
 WHEN status='Deferred' THEN 4
 ELSE 5 END AS 'st',
CASE WHEN priority='Immediate' THEN 0
 WHEN priority='High' THEN 1
 WHEN priority='Medium' THEN 2
 WHEN priority='Low' THEN 3
 ELSE 4 END AS 'p',
CASE WHEN severity='Critical' THEN 0
 WHEN severity='Severe' THEN 1
 WHEN severity='Important' THEN 2
 WHEN severity='Minor' THEN 3
ELSE 4 END AS 's'
FROM ticket
WHERE status != 'Closed'
ORDER BY st, p, s, tkt_mtime)


*** Counters ***

SELECT
  CASE WHEN status IN ('Open','Verified') THEN '#f2dcdc'
   WHEN status='Blocked' THEN '#ff'
   WHEN status='Review' THEN '#e8e8e8'
   WHEN status='Fixed' THEN '#cfe8bd'
   WHEN status='Tested' THEN '#bde5d6'
   WHEN status='Deferred' THEN '#cacae5'
   ELSE '#b8b8b8' END AS 'bgcolor',
  status AS 'Status',
  count (*) AS 'Number of tickets'
FROM ticket GROUP BY status
UNION
SELECT '#ff', 'Total', count(*)
FROM ticket
ORDER BY status

2012/5/31 Chen, Zon zc...@portphillip.vic.gov.au:

 Hi, I'm setting some reports for our Fossil ticket system, but I'm not 
 immediately familiar with SQL.  I've been muddling my way through with the 
 SQLLite documentation, but it would be really nice to see/steal some common 
 examples, such as the reports available on the fossil-scm.org.

 Would it be possible to please make the SQL of the reports used by the fossil 
 project viewable by anonymous users?  Or alternatively, if they could be 
 cut-pasted into the wiki.

 Thanks,
 zchen

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] A draft of ranges contribution

[Jacek Cała]

  Dear Richard, All,

Finally, I've found a bit of time to implement the first draft of the
ranges functionality I was posting a couple of months ago
(http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg07419.html).

This is my first contribution to the project so apologize if anything
is not that clean and tidy as it should be.

From a user point of view the patch changes the way users can do
commits. First 'fossil changes' lists changes with additional column
indicating the row number, e.g.:

  1 EDITED src/checkin.c
  2 EDITED src/main.mk
  3 EDITED src/makemake.tcl
  4 ADDED  src/ranges.c
  5 EDITED win/Makefile.dmc
  6 EDITED win/Makefile.mingw
  7 EDITED win/Makefile.msc

Then using 'fossil commit --range|-r RANGE_LIST' the user can easily
pick only these files they want to check-in, e.g. 'fossil commit -r
1,3-4 -m added an extension to...' is equivalent to 'fossil commit
-m added an extension to... src/checkin.c src/makemake.tcl
src/ranges.c'

Internally, 'fossil changes' creates a temporary table in _FOSSIL_
where it stores row numbers, vfile.id and pathname. This is enough to
restore the proper file ids during 'fossil commit -r ...' and also
detect some circumstances which prevent from safe commit using
ranges. For example, if after above 'fossil changes' the user issues
'fossil rm src/main.mk' and then 'fossil commit -r 2', the code will
complain and guide the user to refresh the changes list.

I'd be glad if anyone can have a look on this and exercise the code to
see if the approach is reasonable.

If you like it, the next target might be 'fossil rm' and then 'fossil
extra' and 'fossil add'.

P.S. After patching the code please issue 'tclsh makemake.tcl' in the
'src' directory to regenerate src/main.mk and win makefiles.

  Cheers,
  Jacek


ranges.patch
Description: Binary data
#include config.h
#include ranges.h
#include errno.h

/*
**
**
*/
static int parse_file_range_token(const char* rangeString, int* range, int startIndex) {
  char* endptr;
  errno = 0;
  range[startIndex] = strtol(rangeString, endptr, 10);

  if (errno != 0 || range[startIndex] = 0) {
fossil_fatal(error parsing ranges);
  } else if (*endptr == '-') {
char* upper = endptr;
range[startIndex + 1] = strtol(upper, endptr, 10);

if (errno != 0 || *endptr != '\0' || range[startIndex + 1] == 0) {
  fossil_fatal(error parsing ranges);
}

return 2;
  } else if (*endptr != '\0') {
fossil_fatal(error parsing ranges);
  }

  return 1;
}


/*
** Parses a string into an array of integers denoting value ranges. 
** The acceptable input string is in form: \d+((-\d+)?(,\d+)?)* 
** For example: '1', '1,2', '1-5,7', '1-3,20-25,9' are all acceptable.
**
** The returned array is zero-terminated and allocated on the heap.
** Negative values indicate an upper bound of a range and must be preceded by
** a positive value -- the lower bound.
**
** For the above examples the function will return following arrays:
** [1], [1, 2], [1, -5, 7], [1, -3, 20, -25, 9]
**
*/
int* parse_file_range(const char* rangeString) {
  /* An arbitraty initial value; must be larger than 2. */
  int reallocLimit = 20;
  char *comma;
  int *range = fossil_malloc(sizeof(int) * reallocLimit);
  int n = 0;
  while ((comma = strchr(rangeString, ',')) != NULL) {
*comma = 0;
n += parse_file_range_token(rangeString, range, n);
*comma = ',';
rangeString = comma + 1;

if (n = reallocLimit - 2) {
  reallocLimit *= 2;
  range = realloc(range, sizeof(int) * reallocLimit);
	 }
  }

  n += parse_file_range_token(rangeString, range, n);
  range[n] = 0;
  return range;
}


/*
** This is a helper function that prints contents of an integer range on 
** standard output.
**
*/
void print_file_range(int* range) {
  int i = 0;
  printf(Range: );
  while (range[i] != 0) {
printf(%d , range[i++]);
  }
  printf(\n);
}

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] New CSS on the Fossil homepage

[Jacek Cała]

Actually, the thing I like most is the rotated skeleton. BTW, have you
considered a different logo. For me fossils usually associate with
ammonites, like:

http://commons.wikimedia.org/wiki/File:Haeckel_Douvilleiceras_mammillatum.jpg
http://en.wikipedia.org/wiki/File:Haeckel_Ammonitida.jpg
http://en.wikipedia.org/wiki/Ammonoidea

If you like it then perhaps there's someone on the list with enough
talent to produce a nice logo from one of the Haeckel ammonites.

  Cheers,
  Jacek

2012/3/31 Richard Hipp d...@sqlite.org:


 On Sat, Mar 31, 2012 at 12:13 PM, Baptiste Daroussin
 baptiste.darous...@gmail.com wrote:

 2012/3/31 Stephan Beal sgb...@googlemail.com:
  On Sat, Mar 31, 2012 at 5:37 PM, Richard Hipp d...@sqlite.org wrote:
 
  I have succumbed to the temptations of eye-candy.  Please offer your
  thoughts and constructive comments on the new look of the Fossil
  website
  versus the previous style.
 
 
  i like the corners, but the background seems a bit too 1998. i like the
  rotated skeleton, too. My roommate says the background clashes too much
  with
  the site's colors.
 
  --
  - stephan beal
  http://wanderinghorse.net/home/stephan/
  http://gplus.to/sgbeal
 

 Everything is nice, but please forget about the background :)



 So now I have three variants up for consideration:

   (1)  http://www.fossil-scm.org/
   (2)  http://www2.fossil-scm.org/
   (3)  http://www3.fossil-scm.org/

 #1 is the recent change, with the rock background, which I (being very old
 school) prefer.  #2 is the original before recent changes.  #3 is like #1
 but without the background image.

 Please continue with feedback.


 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] pushing/pulling the configuration of ticket pages

[Jacek Cała]

  Hi All,

I customized ticket pages 'New Ticket Page' and 'Edit Ticket Page' and
wanted these changes to be distributed to other users. Unfortunately,
doing 'fossil pull -R arepo.fossil' seems not to work.

Is there any way to synchronize these and other report pages?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Behavior of rm, mv, and changes/extra

[Jacek Cała]

(n+1): As mentioned in some of my earlier posts (see [1]), I would be
great to have an ability to {commit | diff | maybe other file related
commands} using ranges like 'fossil commit --range 1,3-4' where
numbers correspond to the file order as presented by 'fossil chan'.
This is more like feature request, though.


[1] http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg07419.html

  Best regards,
  Jacek


2012/2/28 Richard Hipp d...@sqlite.org:


 On Tue, Feb 28, 2012 at 2:06 AM, Gour g...@atmarama.net wrote:

 On Wed, 21 Dec 2011 12:25:19 -0500
 Richard Hipp d...@sqlite.org wrote:

  I fear to change it now, though, since it might really mess up people
  who are used to the older style.

 What about having something like:

 fossil rm --force|-f FILE1 FILE2 ...

 where using '--force' option would make Fossil remove files fromn *both*
 the project and the disk?


 I'm leaning more toward Fossil 2.0 that has a number of incompatible changes
 to the command-line interface, such as having fossil rm and fossil mv
 actually delete and rename the files.  To be clear, the repository file
 format and the sync protocol would continue to be compatible, so Fossil 1.x
 can interact with Fossil 2.x projects.  Only the operation of the various
 fossil commands would change, and only in ways that improve the interface,
 based on past experience.

 Assuming we go with Fossil 2.0, can somebody propose a list of interface
 changes that are needed.  We don't want to repeat this exercise if it can be
 avoided, so let's fix everything all at once.  Here's a start:

 (1)  fossil rm removes the files from the disk
 (2)  fossil mv renames the files on disk




 Sincerely,
 Gour


 --
 The senses are so strong and impetuous, O Arjuna,
 that they forcibly carry away the mind even of a man
 of discrimination who is endeavoring to control them.

 http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] An idea to make command line life easier

[Jacek Cała]

Hi all,

I've just got an idea about how to improve the use of fossil command
line a bit. The main thing is to add an additional index column when
running 'fossil changes', so instead of:

 fossil cha

EDITEDsomefile.x
EDITEDdir\anotherone.xx
EDITEDdir\somefile.x
...

it would produce:

 fossil cha

1  EDITED   somefile.x
2  EDITED   dir\anotherone.xx
3  EDITED   dir\somefile.x
...

Given the index a number of commands, like commit, diff, delete, could
not only take file names as the input argument but also a number, a
list of numbers, a range, etc.
Then, to commit one could use sth like:

 fossil commit -m Some changes in dir --filerange [2-3]

or

 fossil commit -m Some changes in somefiles --filerange 1,3

or any combination of these.

I've looked into the source code and it seems that it would not be too
difficult to implement (at least for commit; I didn't look thoroughly)
but first would like to know your opinion if you would find that
useful. Also, could Richard, Stephan and others who spent more time on
fossil development say if this is really possible or rather I overlook
something and there is an inherent flaw in the idea.

  Many thanks,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to limit fossil diff output to just names of the changed files?

[Jacek Cała]

Try 'fossil changes'

  Cheers,
  Jacek

2012/1/31 Leo Razoumov slonik...@gmail.com:
 Hi All,
 I am a new Fossil SCM user and it is my first posting to this mailing
 list. Please, forgive me if what I am asking has been discussed and
 answered here before.

 When I do
     sh$ fossil diff --from ver1 --to ver2
 I get the entire contextual diff of the changes between the said commits.

 How could I get only the _names_ of the changed  files _without_
 contextual differences?
 Something like git diff --name-status or git diff --name-only.

 I know I can see the list of the names of changed files via fossil ui but
 I prefer to list the files using fossil command line interface, for I
 can grep the output further.

 --Leo--
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] An idea to make command line life easier

[Jacek Cała]

Hmm... Clearly, it can be scripted in perl (@James) and in bash/awk
(@Lluís) and using other tools but:

1. The use of, say, '-r 1-3' syntax is much more convenient than
piping to awk everytime I need a selective commit, diff or alike.
2. Writing/using a separate perl/bash/whatever script seems much not
like the fossil many-in-one approach.
3. I'm on a win box and don't {have/want} to install
perl/cygwin/whatever to get tools, to build scripts, to use such a
feature.
4. As Stephan suggested, it seems not too difficult to implement.
5. Perhaps it is even not too costly to run everytime we need a
selective command.

More opinions welcome.

  Cheers,
  Jacek


2012/1/31 Lluís Batlle i Rossell vi...@viric.name:
 On Tue, Jan 31, 2012 at 06:45:11PM +, Jacek Cała wrote:

 How would it be different than:
  fossil changes | awk '{ print NR   $0; }'

 or with your filter on lines:
  fossil changes | awk '{ if(NR = 3  NR = 4) print NR   $0; }'


 Regards,
 Lluís.
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Check-Ins Associated With a Ticket

[Jacek Cała]

  Hi all,

I've just noticed that there's link 'Check-ins' in the View Ticket
page. Clicking on this I can see page 'Checkins Associated With Ticket
xxx' which in my case is empty. Looks like this is somewhat related to
a thing I was discussing some time ago
(http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg01662.html).

Now the question: how can I associate a check-in with a ticket?

  Best regards,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] A little self-promotion

[Jacek Cała]

And, most of all, for users it makes documentation just a click away.

  Cheers,
  Jacek

2011/11/16 Steve Havelka smh...@gmail.com:
 On 11/16/11 4:11 PM, Ron Wilson wrote:

 On Wed, Nov 16, 2011 at 4:15 PM, Jacek Całajacek.c...@gmail.com  wrote:

 and wonder why
 fossil is by default so humble to not include a link to its web site
 in the footer.

 Maybe to encourage users to contact their project leader first?

 In my team, I've been handling the questions.

 For public-facing repos, this is a great idea.  It's like how Wordpress has
 its link at the bottom of the default theme, a cheap and easy way to bring
 more people to the project.  I'm not sure if anyone would actually be
 confused about whose project it is, just by the presence of that link.


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] A little self-promotion

[Jacek Cała]

  Hi all,

Just been preparing a project site based on fossil and wonder why
fossil is by default so humble to not include a link to its web site
in the footer. Basically, I'd change this:

div class=footer
Fossil version $release_version $manifest_version $manifest_date
/div
/body/html

to:

div class=footer
a style=color:white;text-decoration:none
href=http://fossil-scm.org; target=_blankFossil/a version
$release_version $manifest_version $manifest_date
/div
/body/html

or perhaps some version that uses CSS.

It shouldn't hurt anyone and even make life a little bit easier for
users, I believe.

  Best,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] [best practice] Including external dependencies

[Jacek Cała]

  Hi all,

A best practice question:
What is the preferred way to include external libraries in a fossil
repository? I mean larger dependencies like boost.
For small libs and tools like a few binary or source code files, I
tend to include them directly in the repo but for larger ones it
doesn't seem like a proper approach, esp. when the library code is
much larger than my sources.

On stackoverflow I read that git to address this issue has something
called 'subprojects'
(http://stackoverflow.com/questions/2994005/including-external-c-libraries-in-version-control).
Has anyone used that? Is creating a separate fossil repo with the
library files an equivalent way?

  Thanks,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Linking to fossil.exe [Re: GUI client for Windows?]

[Jacek Cała]

Hi Stephan, All

I've just realized that despite fossil is an executable it does not
prevent if from exporting functions for other programs to use (at
least on Windows, am not sure if this is possible on *nix).

I've just made a simple test executable Prog1.exe that links to
another executable Prog2.exe. You can run Prog2.exe normally (it has
it's own main function), but also you can link to it and use the
functions it exports. My Prog1.exe uses a test function from
Prog2.exe. All works as a breeze!

A quick look on wikipedia and PE format
(http://en.wikipedia.org/wiki/Portable_Executable) shows that PE is
somewhat related to a unix COFF format. Perhaps the same trick is
possible on *nix platforms. I think that it would solve a lot of pain
in creating JSON API.

  Best regards,
  Jacek


2011/10/6 Stephan Beal sgb...@googlemail.com:
 On Thu, Oct 6, 2011 at 12:02 PM, Gilles gilles.gana...@free.fr wrote:

 Thanks for the info. Out of curiosity, what do you mean by monolithic
 design, and why is it a problem to write a GUI?

 Fossil is a standalone application, not a C library of functionality. That
 means that in order to write a UI the only possibility you have is to parse
 the command-line output. Since fossil makes no guarantees about output
 format, it's basically impossible (or, long-term, futile) to try to create a
 UI in this way. This worked (barely) with CVS because CVS had well-defined
 output formats (where as fossil is more free form (which i happen to
 prefer, so that isn't a complaint)).
 The JSON API effectively adds a library interface (of a sort) to fossil,
 which allows other applications to call specific functions of fossil and get
 well-defined responses which are easily parsed (JSON format) and understood.
 For example, we can write a shell-like interface which communicates with a
 fossil instance over JSON, hiding the JSON bits from the user in the form of
 command-shell-style input and output.
 More infos about the JSON API (still incomplete, but can already do a good
 deal) can be found here:
 https://docs.google.com/document/d/1fXViveNhDbiXgCuE7QDXQOKeFzf2qNUkBEgiUvoqFN4/edit?hl=en_US
 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Linking to fossil.exe [Re: GUI client for Windows?]

[Jacek Cała]

2011/10/6 Stephan Beal sgb...@googlemail.com:
 2011/10/6 Jacek Cała jacek.c...@gmail.com

 A quick look on wikipedia and PE format
 (http://en.wikipedia.org/wiki/Portable_Executable) shows that PE is
 somewhat related to a unix COFF format. Perhaps the same trick is
 possible on *nix platforms. I think that it would solve a lot of pain
 in creating JSON API.

 It wouldn't save much, if any, in this case. In writing the JSON API i often
 have to minorly refactor existing fossil functionality or change its
 visibility from static to non-static so that the json code can use it. More
 often than not i have to create separate impls for the JSON variant of a
 given call because the original variants generate output to stdout (which is
 absolutely taboo in JSON mode, and must be avoided at all costs because it
 would corrupt the output). If i were using fossil.exe as a library (of
 sorts) i couldn't do that - i would still be limited to the set of features
 which are not static. Whether or not a function in fossil is static is
 almost arbitrarily decided - if the function is only used in one file, it's
 typically static, else it is not static.

Agree, however, I thought that JSON API was the solution for linking
external apps to fossil, and hence having ability to call fossil
directly would make the API redundant. But, obviously, the API may be
needed for some other reasons as well.

Nonetheless, I think that (at least for windows builds) exporting
fossil functions for others to link to is a viable and valuable
option.

  Regards,
  Jacek


 - stephan beal
 http://wanderinghorse.net/home/stephan/

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Linking to fossil.exe [Re: GUI client for Windows?]

[Jacek Cała]

Is this too much hassle to improve the exec in this matter? As said
@Stephan, I think that this option is much more viable than using any
intermediaries like standard output/error, protocol buffers or JSON
API. What do you think? I could spent a bit of my time and look at it
if this is doable and anyone is interested.

  Cheers,
  Jacek

2011/10/6 Dmitry Chestnykh dmi...@codingrobots.com:
 On Oct 6, 2011, at 16:59 , Jacek Cała wrote:

 I've just realized that despite fossil is an executable it does not
 prevent if from exporting functions for other programs to use (at
 least on Windows, am not sure if this is possible on *nix).

 It doesn't matter how the program is linked. Fossil calls exit() when a 
 function needs to fail, and it leaves it up to the OS to clean up allocated 
 memory.

 --
 Dmitry Chestnykh

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Diff after move

[Jacek Cała]

  Hi All,

I moved some files from one dir to another and made some changes.
Issuing 'fossil chan' showed me that the files are missing - correct.
I ran 'fossil mv' on these files and then 'fossil chan' showed that
they're edited - correct. However, when I try to see the changes
'fossil diff' I get:

fossil.exe: file XXX does not exist in checkin:

Can't say if that matters but all above was after moving my repository
from its original place and issuing 'fossil open
REPO_IN_A_NEW_PLACE.fossil --keep'

I wouldn't like to make commit on my sources until I see the changes,
so any help appreciated

  Regards,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Diff after move

[Jacek Cała]

Hi Stephan,

Actually, I moved the files. Sorry, forgot to add that my first
'fossil chan' reported some MISSING files which I found after running
'fossil extra'. This allowed me to let fossil know that the files were
moved by running 'fossil mv'. And so this my question: why fossil
can't find them in the new place if I can clearly see they're there?
Also 'fossil ls' shows they're in the new dir.

I suspect that 'fossil diff' tries to search for previous versions in
the new dir instead of the old one. That could explain the problem.

Have anyone seen anything similar?

  Jacek

W dniu 1 września 2011 16:14 użytkownik Stephan Beal
sgb...@googlemail.com napisał:
 2011/9/1 Jacek Cała jacek.c...@gmail.com

 fossil.exe: file XXX does not exist in checkin:

 You also need to do the mv yourself. fossil mv records the intention but
 does not actually perform the mv on the filesystem.


 Can't say if that matters but all above was after moving my repository
 from its original place and issuing 'fossil open
 REPO_IN_A_NEW_PLACE.fossil --keep'

 That shouldn't matter, as long as you re-open after moving your fsl file.

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Diff after move

[Jacek Cała]

Hi again,

I made a test on a simple, one file repository with two dirs:

DirA\file.txt
DirB\

I created a new repo, added DirA/file.txt, commited, made some
changes, moved file to 'DirB', issued 'fossil chan' - saw the MISSING
file, issued 'fossil extra' - saw DirB/file.txt. Issued 'fossil mv
DirA/file.txt DirB/file.txt' then 'fossil chan' - saw EDITED
DirB/file.txt. And, finally, 'fossil diff DirB/file.txt' resulted in
'fossil.exe: file DirB/file.txt does not exist in checkin:'

Looks like a bug in the diff command but please confirm it if you can.
My 'fossil ver' - 'This is fossil version 1.18 [df9da91ba8]
2011-07-13 23:03:41 UTC'; OS: 'Windows 7 x64'

  Regards,
  Jacek


W dniu 1 września 2011 16:39 użytkownik Jacek Cała
jacek.c...@gmail.com napisał:
 Hi Stephan,

 Actually, I moved the files. Sorry, forgot to add that my first
 'fossil chan' reported some MISSING files which I found after running
 'fossil extra'. This allowed me to let fossil know that the files were
 moved by running 'fossil mv'. And so this my question: why fossil
 can't find them in the new place if I can clearly see they're there?
 Also 'fossil ls' shows they're in the new dir.

 I suspect that 'fossil diff' tries to search for previous versions in
 the new dir instead of the old one. That could explain the problem.

 Have anyone seen anything similar?

  Jacek

 W dniu 1 września 2011 16:14 użytkownik Stephan Beal
 sgb...@googlemail.com napisał:
 2011/9/1 Jacek Cała jacek.c...@gmail.com

 fossil.exe: file XXX does not exist in checkin:

 You also need to do the mv yourself. fossil mv records the intention but
 does not actually perform the mv on the filesystem.


 Can't say if that matters but all above was after moving my repository
 from its original place and issuing 'fossil open
 REPO_IN_A_NEW_PLACE.fossil --keep'

 That shouldn't matter, as long as you re-open after moving your fsl file.

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users



___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Diff after move

[Jacek Cała]

  Hello once again,

Having no choice I had to commit the changes without prior view. And
now from the UI I can do the diff as expected and see changes in the
files that were moved.

  Regards,
  Jacek


W dniu 1 września 2011 17:00 użytkownik Jacek Cała
jacek.c...@gmail.com napisał:
 Hi again,

 I made a test on a simple, one file repository with two dirs:

 DirA\file.txt
 DirB\

 I created a new repo, added DirA/file.txt, commited, made some
 changes, moved file to 'DirB', issued 'fossil chan' - saw the MISSING
 file, issued 'fossil extra' - saw DirB/file.txt. Issued 'fossil mv
 DirA/file.txt DirB/file.txt' then 'fossil chan' - saw EDITED
 DirB/file.txt. And, finally, 'fossil diff DirB/file.txt' resulted in
 'fossil.exe: file DirB/file.txt does not exist in checkin:'

 Looks like a bug in the diff command but please confirm it if you can.
 My 'fossil ver' - 'This is fossil version 1.18 [df9da91ba8]
 2011-07-13 23:03:41 UTC'; OS: 'Windows 7 x64'

  Regards,
  Jacek


 W dniu 1 września 2011 16:39 użytkownik Jacek Cała
 jacek.c...@gmail.com napisał:
 Hi Stephan,

 Actually, I moved the files. Sorry, forgot to add that my first
 'fossil chan' reported some MISSING files which I found after running
 'fossil extra'. This allowed me to let fossil know that the files were
 moved by running 'fossil mv'. And so this my question: why fossil
 can't find them in the new place if I can clearly see they're there?
 Also 'fossil ls' shows they're in the new dir.

 I suspect that 'fossil diff' tries to search for previous versions in
 the new dir instead of the old one. That could explain the problem.

 Have anyone seen anything similar?

  Jacek

 W dniu 1 września 2011 16:14 użytkownik Stephan Beal
 sgb...@googlemail.com napisał:
 2011/9/1 Jacek Cała jacek.c...@gmail.com

 fossil.exe: file XXX does not exist in checkin:

 You also need to do the mv yourself. fossil mv records the intention but
 does not actually perform the mv on the filesystem.


 Can't say if that matters but all above was after moving my repository
 from its original place and issuing 'fossil open
 REPO_IN_A_NEW_PLACE.fossil --keep'

 That shouldn't matter, as long as you re-open after moving your fsl file.

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] trouble with 'localauth'

[Jacek Cała]

  Hi all,

I can confirm that there is some problem with automatic log in from
localhost. I tried setting localauth and using '--localauth' option
and both 'server' and 'ui' and couldn't get it.

My fossil is the latest binary distribution: 13/04/2011,
running on win7 and opera.

  Regards,
  Jacek

 Hi,
 I've been only occasionally using the web ui on fossil in the last few
 months,
 but I seem to have developed a problem with localauth.

 I forst noticed it when it seemed that I wasn't being automatically logged
 in.

 I have since done a test (see below) where I create a new repository, then
 attempt to login with fossil ui tracker.fossil

 Is anyone else getting this?
 (I'm on win7, IE8)

 Cheers,

 Stephen
 --
 Stephen De Gabrielle
 stephen.degabrie...@acm.org
 Telephone +44 (0)20 85670911
 Mobile+44 (0)79 85189045
 http://www.degabrielle.name/stephen
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] trouble with 'localauth'

[Jacek Cała]

The same for me

fossil new xxx.fossil
fossil ui xxx.fossil

does not log in me automatically (Opera, Firefox).

I forgot to add I use x64 win7. Perhaps it matters that this is x64 or
win7 x64. Anyone else with different win or win7 x32?

  Regards,
  Jacek

2011/5/6 Tomek Kott tkott.s...@gmail.com:
 On Fri, May 6, 2011 at 11:49 AM, Richard Hipp d...@sqlite.org wrote:


 On Fri, May 6, 2011 at 11:00 AM, Tomek Kott tkott.s...@gmail.com wrote:

 oh, then in that case, I have a problem with it as well :)

 I'm using:
    This is fossil version [047e06193b] 2011-04-13 12:05:18 UTC

 On a windows-7 64 bit machine, with the pre-compiled version downloaded
 from the website.

 I did the following commands:

 fossil new random.fossil
 fossil set localauth 1 -R random.fossil

 The command above changes the defaults such that login is required.  Only
 do that if you really want to force people to log in when running fossil
 ui.

 Oh, right, that's a RTFM moment... sorry.



 fossil set  -R random.fossil  To check that localauth was set
 fossil ui -R random.fossil

 Try that:

     fossil new whatever.fossil
     fossil ui whatever.fossil


 The does NOT give me acess to the 'whatever' repository.

 Is there somewhere we can download a newer windows build of Fossil except
 from http://www.fossil-scm.org/download.html, which only has the 4/13
 version?

 Thanks,

 Tomek


 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] http-port settings

[Jacek Cała]

Possibly, although I can't remember I set anything in particular
except for global settings. Where can I set the local settings?

  Jacek

W dniu 9 lutego 2011 06:41 użytkownik Heinrich Huss
heinrich.h...@psh-consulting.de napisał:
 I think the local setting of the repository is set to 8080 and
 overwrites the global one

 Regards
 Hein
 Am 08.02.2011 um 23:10 schrieb Jacek Cała:

 Hmmm... On my Windows box it looks like this:

 C:\fossil settings http-port
 http-port            (global) 8081

 C:\fossil server c:\apps\fossil.repo\vertical-deployment.fossil
 Listening for HTTP requests on TCP port 8080
 Type Ctrl-C to stop the HTTP server

 So looks like this is an OS dependent issue.

  Cheers,
  Jacek


 2011/2/8 Remigiusz Modrzejewski l...@maxnet.org.pl:

 On Feb 8, 2011, at 16:55 , Jacek Cała wrote:

  Hi all,

 I tried in vain to set different http port with command 'fossil
 settings http-port'. Regardless of the settings running 'fossil
 server
 ...' or 'fossil ui ...' ends up on 8080.

 Any ideas or this is just a bug?

 $ fl setting http-port 12345
 $ fl server  curl http://localhost:12345/
 [1] 10729
  % Total    % Received % Xferd  Average Speed   Time    Time
 Time  Current
                                 Dload  Upload   Total   Spent
 Left  Speed
 100    63  100    63    0     0   6039      0 --:--:-- --:--:--
 --:--:--  7875
 html
 pRedirect to http://localhost:12345/index/p
 /html


 Kind regards,
 Remigiusz Modrzejewski



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-
 users

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] http-port settings

[Jacek Cała]

  Hi all,

I tried in vain to set different http port with command 'fossil
settings http-port'. Regardless of the settings running 'fossil server
...' or 'fossil ui ...' ends up on 8080.

Any ideas or this is just a bug?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] ticket notifications

[Jacek Cała]

Regarding tickets notification, it would be nice if opening/closing tickets
allow starting/stopping time measurement. In this way fossil could count up
how long it takes to complete tasks. This would be more intentional than in
eclipse's mylyn but still very useful.

  Regards,
  Jacek

2010/6/24 Richard Hipp d...@sqlite.org

 There is nothing in principle that would prevent such functionality from
 being added.  But on the other hand, no such functionality currently exists.

 Notice that the issue is complicated by the fact that ticket changes can
 occur on disconnected systems.  When are the emails sent?  When the
 disconnected system syncs with the server that is doing the emailing,
 perhaps?


 On Thu, Jun 24, 2010 at 2:18 PM, Jeff Rogers dv...@diphi.com wrote:

 Hi all,

 Is there a way to set up the ticket system to send email notifications
 when a ticket is created (or changed, etc)?  There doesn't appear to be
 any way in TH1 to run an external command (like sendmail)

 Alternately, is there a command-line way to list any tickets created in
 the past X (e.g., 1 day), so that a cronjob could check for new tickets
 and send mail?

 Thanks
 -J
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users




 --
 -
 D. Richard Hipp
 d...@sqlite.org

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] ticket notifications

[Jacek Cała]

Thanks for ideas I'll try to play with this.

  Jacek

2010/6/24 Joshua Paine jos...@letterblock.com

 On 06/24/2010 02:39 PM, Jacek Cała wrote:
  Regarding tickets notification, it would be nice if opening/closing
  tickets allow starting/stopping time measurement. In this way fossil
  could count up how long it takes to complete tasks.

 IMO this is way, way out of scope for fossil, but it wouldn't be hard to
 build such reports yourself by reading the fossil db or just checking
 the timeline rss periodically.

 http://yourserver/path/to/repo/timeline.rss?n=200y=t gives you the
 last 200 ticket-related events, and it would be trivial to parse with an
 RSS lib, an XML lib, or just a couple regex.

 --
 Joshua Paine
 LetterBlock: Web applications built with joy
 http://letterblock.com/
 301-576-1920
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Feature request: commit a ticket

[Jacek Cała]

[...@ramon] Hmmm, yes and no.

fossil ticket...

would give more versatility but again it would require two steps instead of
one.

[...@ronald] Yes, if you need multiple checkins this option would require
another parameter, like '-s status'

[...@ron] This might be a little hassle when there is one commit which fixes
multiple tickets.

All in all, maybe something like this:

fossil -t ticket_id,ticket_id,... -m comment [-s status_type] [-r
resolution_type]

other option is what Ramon suggested:

fossil ticket...

Personally, I would prefer the former.

  Jacek

2010/3/15 Ramon Ribó ram...@compassis.com

   If there was a command:

 fossil ticket ...

 similar to fossil wiki ..., it would be easy to implement this
 functionality in the graphical interface instead to trying to do it
 directly in the command line.

  In this way, more versatility would be possible without making the
 command line interface more complex to learn for a beginner.

 
 Compass Ing. y Sistemas Dr. Ramon Ribo
 http://www.compassis.com  ram...@compassis.com
 c/ Tuset, 8 7-2  tel. +34 93 218 19 89
 08006 Barcelona, Spainfax. +34 93 396 97 46



 2010/3/15 Wilson, Ronald rwils...@harris.com:
  also, sometimes a single ticket requires multiple checkins over time
  to arrive at a fix.
 
  rw
 
  from my mobile 434.851.1612
 
  On Mar 14, 2010, at 12:53 PM, Jeremy Cowgar jer...@cowgar.com wrote:
 
  On 3/13/2010 7:32 PM, Jacek Cała wrote:
  fossil commit -t ticket_id -m comment [-r resolution_type]
 
  I like the idea. Only one problem, as I see it though. Maybe
  discussion
  can bring about it's resolution. Maybe it's just a change of my
  workflow, don't know. I'll get a few minor bug's submitted then sit
  down
  to a coding session. Often times a bug is just a one word/line change.
  I'll fix the minor bugs and commit a message such as:
 
*  Fixed [384938]. Blah Blah Blah
*  Fixed [2939283]. Blah Blah Blah.
 
  Does everyone do the same or does everyone fix one bug per commit?
 
  Jeremy
 
  ___
  fossil-users mailing list
  fossil-users@lists.fossil-scm.org
  http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
  ___
  fossil-users mailing list
  fossil-users@lists.fossil-scm.org
  http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
 
 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Feature request: commit a ticket

[Jacek Cała]

  Hi All,

What do you think about the following feature?

The case is very common, I suppose. Let's have an issue reported by a
tester/user as a ticket. When a developer resolves the issue they would like
to commit changes that are related to the ticket describing this issue.
AFAIK in fossil tickets are completely separated from code commits, it means
that often I need to do two things: first, commiting changes and then
closing a ticket. Both these need providing a comment, which I think should
be more or less the same.

Wouldn't be useful if this common case is simplified to only a single
operation: commit which closes a related ticket e.g. using a command like:

fossil commit -t ticket_id -m comment [-r resolution_type]

This should close ticket ticket_id supplying a comment as the
explanation of the resolution. Optionally, one could provide a type of
resolution which is one from the ticket resolution list; by default this
could be 'fixed'.

What do you think?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Done a helpful hint. Was: Export repo

[Jacek Cała]

Thanks for this! This will be really useful.

  Jacek

2010/3/11 D. Richard Hipp d...@hwaci.com

 See http://www.fossil-scm.org/fossil/ci/2582ecf2ed

 A helpful hint (which applies to more than just the zip command):

 In most places where a version or check-in name is request, you
 can substitute a branch name or a tag and it will use the most recent
 check-in on that branch or the most recent check-in with the given
 tag.  So for example, we tag certain check-ins in Fossil with
 release to indicate that they are check-ins that are officially
 released.  To generate a ZIP archive of the most recent release:

  fossil zip release output.zip

 If you have a separate branch named experimental, you can get the
 most recent check-in of that branch using:

 fossil zip experimental output.zip

 You can also substitute an ISO8601 date and time to get the most
 recent check-in prior to the specified date:

 fossil zip 2009-11-05 18:00:00 output.zip

 If you want the most recent version of a branch prior to a date, put
 the branch name first followed by the date, and separated by a colon:

 fossil zip experimental:2009-11-05 18:00:00 output.zip

 All of these forms apply to most commands.  For example:

 fossil update experimental:2009-11-05 18:00:00
 fossil merge trunk
 fossil open repo.fossil in-test

 All of the above forms also apply to URLs.  So, for example, to see
 what the Fossil website looked like on trunk branch on July 4, 2009:

 http://www.fossil-scm.org/fossil/doc/trunk:2009-07-04/www/
 index.wiki

 Or to get the details of the check-in that is the latest release:

 http://www.fossil-scm.org/fossil/info/release

 And so forth   Yes, you're right:  I need to document this
 someplace

 D. Richard Hipp
 d...@hwaci.com



 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Not all tickets are problems

[Jacek Cała]

For me tickets are ok and by default you have type 'Task' configured.
If you create a report that filters by this, isn't it enough?

  Regards,
  Jacek


2010/2/10 Ron Aaron r...@ronware.org

 Concerning ticket [2b79f36e5a], I agree with the notion.  However,  I would
 take it a bit further and say issues rather than tickets, throughout
 the
 product.  I would also add a Todo type (well, I have in my own projects),
 as
 Fossil is an excellent way to keep track of meta-issues as well as actual
 bugs
 or work-items.

 Comments?

 --
 For privacy, my GPG key signature is: AD29415D

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Numbering in the ticket view

[Jacek Cała]

Hi,

Do you have any idea how to add numbering to the list of tickets. It would
be nice to have a quantitative view on the solved/unsolved issues. I was
skimming through the sqllite manual but couldn't find anything usable.

  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Ticket system - blockers

[Jacek Cała]

Hi all,

I wonder if there is any simple way to add `blocker' feature to the fossil's
ticketing system (I mean a list of tickets that prevent one to complete). I
tried adding 'CREATE TABLE blocker(...)' in the Admin-Tickets-Table page
and then when creating a new ticket report it says:

* **Syntax error: access to blockers.blockerid is prohibited*

Is there any way to access a second table from the UI?
Do you have any other ideas?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] add rm directory

[Jacek Cała]

Hi,

I noticed a kind of asymmetry between 'add' and 'rm' commands. While it is
possible to add directory contents to a repository I cannot find a way to
easily remove it.

 fossil add my_dir
works fine, whereas
 fossil rm my_dir

does not. Am I missing something?

  Cheers,
  Jacek
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] add rm directory

[Jacek Cała]

Yes, but I meant easy. As easy as fossil add my_dir.

  Jacek


2009/9/25 Stephan Beal sgb...@googlemail.com

 2009/9/25 Jacek Cała jacek.c...@gmail.com

 I noticed a kind of asymmetry between 'add' and 'rm' commands. While it is
 possible to add directory contents to a repository I cannot find a way to
 easily remove it.

  fossil add my_dir
 works fine, whereas
  fossil rm my_dir

 does not. Am I missing something?


 If i'm not mistaken, the way to remove a dir is to remove all files in
 it. Or maybe i'm mis-remembering from my CVS youth (CVS doesn't check out
 empty dirs by default, IIRC).

 --
 - stephan beal
 http://wanderinghorse.net/home/stephan/

 ___
 fossil-users mailing list
 fossil-users@lists.fossil-scm.org
 http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users