Re: [fossil-users] Annotate for wiki pages

2011-03-12 Thread Stephen De Gabrielle
Do you mean in the same way editing a ticket appends by default?
S.

On Friday, March 11, 2011, Lluís Batlle i Rossell virik...@gmail.com wrote:
 Hello,

 is there a way I can get an 'annotate' for wiki pages?

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


-- 

--
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] git equivalent commands

2011-03-12 Thread Federico Ramallo
Thanks for your feedback!

fossil revert worked as expected! Also fossil checkout -f
branch_or_commit_d worked too, but usually you don't want to change the
branch, just remove the changes.

I don't except to have all the features of git, since there are a lot of
different concepts going on with fossil. We are using fossil with the team
in one project for the first time. And we are trying to work the fossil way
considering our workflow. So we are learning.
I just added the git commands to easily explain the actions we are trying to
run, otherwise it would be harder, longer to explain. Furthermore it would
be less accurate.
The reason we are looking for those commands is because during our
development workflow we find out we didn't know how to do certain actions we
used to do with You-know-What ( The-Thing-That-Must-Not-Be-Named )

The grep command is a really great deal for us because:
* We use vim and is the fastest way to search on the entire project (think
of a project with 100M+ with binaries and source code and we are not allowed
to change that)
* Is WAY much faster than grep -R
* is more flexible than Ack (considering searching on .wiki, README and any
other file that is not code)


I think is interesting to know how to rollback a commit. I'm used to just
add a new commit removing the changes. That way we keep the history (made a
mistake, fixed the mistake)

Also, What we couldn't find out is how to delete a branch (or at least close
it)

Regards,
Federico Ramallo
___
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] git equivalent commands

2011-03-12 Thread Federico Ramallo
Awesome! I'll check it out! :D


2011/3/12 Joerg Sonnenberger jo...@britannica.bec.de

 On Sat, Mar 12, 2011 at 09:57:25AM -0600, Federico Ramallo wrote:
  Also, What we couldn't find out is how to delete a branch (or at least
 close
  it)

 Use the web ui. You can mark a branch leaf as closed and you can also
 move commits to different branches / change the tags etc.

 Joerg
 ___
 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] git equivalent commands

2011-03-12 Thread Joshua Paine
On Mar 12, 2011, at 10:57 AM, Federico Ramallo frama...@gmail.com wrote:
 we are trying to work the fossil way considering our workflow. So we are 
 learning.
 I just added the git commands to easily explain the actions we are trying to 
 run,

It's all good. Since many of us are familiar with git, too, it's a very 
reasonable way to proceed.

 The grep command is a really great deal for us because:
 * is more flexible than Ack (considering searching on .wiki, README and any 
 other file that is not code)

You probably know that ack can optionally search all file types or configurable 
file types. You might also try writing yourself a one-line shell script that 
makes use of `fossil ls` (to list all files in the project) and one of the text 
search tools for more control. If the large binaries aren't checked in, then 
this will automatically avoid searching those. If they are, you'll probably 
want to filter the list with grep before searching.

I believe there has been talk of adding search to fossil, but I don't know 
about progress on that if any.

 I think is interesting to know how to rollback a commit. I'm used to just add 
 a new commit removing the changes. That way we keep the history (made a 
 mistake, fixed the mistake)

I thought this just came up, but I can't find it. Of course in fossil you can 
still just add a commit reversing the changes, but another option is to make 
the mistaken commit the start of a new branch named 'oops' or 'mistake' and 
immediately close that branch. The record of the error still exists, but the 
branch timeline is a clearer reference on the actual progress of the code.

(To do this, run `fossil ui`, go to the timeline, click on the mistaken commit, 
click on 'Edit' by 'Other Links:, and use the checkbox and textbox by 
Branching to move the commit to a new branch. You'll want to mark the Leaf 
Closure checkbox as well.) 

 Also, What we couldn't find out is how to delete a branch (or at least close 
 it)

Branches cannot be deleted (nor can much of anything be completely deleted in 
fossil!), but to close the branch, use the Leaf Closure checkbox on the details 
page of the latest commit in the branch.
___
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] git equivalent commands

2011-03-12 Thread Richard Hipp
On Sat, Mar 12, 2011 at 11:33 AM, Joshua Paine jos...@letterblock.comwrote:

  I think is interesting to know how to rollback a commit. I'm used to just
 add a new commit removing the changes. That way we keep the history (made a
 mistake, fixed the mistake)

 ... another option is to make the mistaken commit the start of a new branch
 named 'oops' or 'mistake' and immediately close that branch.


An example of doing exactly that can be seen in SQLite sources here:
http://www.sqlite.org/src/timeline?c=2010-10-01+15%3A11%3A09

I checked in a change that I thought was good.  But later I figured out it
was a bad idea, so I move the change onto the mistake branch, closed that
branch, and amended the check-in commit to explain why it was a bad idea.


-- 
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] Howto construct a download url for the latest file in a repository?

2011-03-12 Thread David Bovill
Is there a syntax for constructing a url which would directly download a
file from the repository? Looking at the way the web site is constructed it
looks like there are only direct urls to a particular artifact - I want to
use a url to link to the latest version of the file, not a particular
artifact.

As an example I have set up a multiple repository we site, and the url to a
particular version of a file looks like this:

   - http://...
   /raw/libOPN_IRC.livecode?name=bf6a5a5751878cf242e2733656554ec131f3657c

If I now update this file, then the above url will no longer point to the
http download url for the latest file. Is there a way to construct this - or
will I have to write a custom cgi that calls fossil via the command line?
___
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] Howto construct a download url for the latest file in a repository?

2011-03-12 Thread David Bovill
On 12 March 2011 17:37, Richard Hipp d...@sqlite.org wrote:


 In the name=NAME part of the URL, the NAME does not have to be a SHA1
 hash.  It can be any of the forms described at
 http://www.fossil-scm.org/fossil/doc/trunk/www/checkin_names.wiki such as
 trunk.  So perhaps you could use:

 http://.../raw/libOPN_IRC.livecode?name=trunk


Hi Richard - the above style url, or
http://.../raw/libOPN_IRC.livecode?name=tip
leads to an http download of the manifest file, not that actual file the
manifest refers to. Any other thoughts?
___
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] Howto construct a download url for the latest file in a repository?

2011-03-12 Thread Richard Hipp
On Sat, Mar 12, 2011 at 5:21 PM, David Bovill da...@architex.tv wrote:

 On 12 March 2011 17:37, Richard Hipp d...@sqlite.org wrote:


 In the name=NAME part of the URL, the NAME does not have to be a SHA1
 hash.  It can be any of the forms described at
 http://www.fossil-scm.org/fossil/doc/trunk/www/checkin_names.wiki such as
 trunk.  So perhaps you could use:

 http://.../raw/libOPN_IRC.livecode?name=trunk


 Hi Richard - the above style url, or  
 http://.../raw/libOPN_IRC.livecode?name=tip
 leads to an http download of the manifest file, not that actual file the
 manifest refers to. Any other thoughts?



http://.../zip/checkout.zip?name=trunk


 ___
 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


Re: [fossil-users] fossil-users Digest, Vol 38, Issue 32

2011-03-12 Thread 曾全贵
Hello,I am a newer of SQLite,I have a problem,how can I learn the
source of SQLite?

2011/3/13, fossil-users-requ...@lists.fossil-scm.org
fossil-users-requ...@lists.fossil-scm.org:
 Send fossil-users mailing list submissions to
   fossil-users@lists.fossil-scm.org

 To subscribe or unsubscribe via the World Wide Web, visit
   http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

 or, via email, send a message with subject or body 'help' to
   fossil-users-requ...@lists.fossil-scm.org

 You can reach the person managing the list at
   fossil-users-ow...@lists.fossil-scm.org

 When replying, please edit your Subject line so it is more specific
 than Re: Contents of fossil-users digest...


 Today's Topics:

1. Re: git equivalent commands (Federico Ramallo)
2. Re: git equivalent commands (Joerg Sonnenberger)
3. Re: git equivalent commands (Federico Ramallo)
4. Re: git equivalent commands (Joshua Paine)
5. Re: git equivalent commands (Richard Hipp)
6. Howto construct a download url for the latest file  in a
   repository? (David Bovill)
7. Re: Howto construct a download url for the latest file in a
   repository? (Richard Hipp)
8. Re: Howto construct a download url for the latest file in a
   repository? (David Bovill)


 --

 Message: 1
 Date: Sat, 12 Mar 2011 09:57:25 -0600
 From: Federico Ramallo frama...@gmail.com
 Subject: Re: [fossil-users] git equivalent commands
 To: fossil-users@lists.fossil-scm.org
 Message-ID:
   AANLkTimFeKbV+-fJs=V-qm0REqRPbgz3uLfP2--2=0...@mail.gmail.com
 Content-Type: text/plain; charset=iso-8859-1

 Thanks for your feedback!

 fossil revert worked as expected! Also fossil checkout -f
 branch_or_commit_d worked too, but usually you don't want to change the
 branch, just remove the changes.

 I don't except to have all the features of git, since there are a lot of
 different concepts going on with fossil. We are using fossil with the team
 in one project for the first time. And we are trying to work the fossil way
 considering our workflow. So we are learning.
 I just added the git commands to easily explain the actions we are trying to
 run, otherwise it would be harder, longer to explain. Furthermore it would
 be less accurate.
 The reason we are looking for those commands is because during our
 development workflow we find out we didn't know how to do certain actions we
 used to do with You-know-What ( The-Thing-That-Must-Not-Be-Named )

 The grep command is a really great deal for us because:
 * We use vim and is the fastest way to search on the entire project (think
 of a project with 100M+ with binaries and source code and we are not allowed
 to change that)
 * Is WAY much faster than grep -R
 * is more flexible than Ack (considering searching on .wiki, README and any
 other file that is not code)


 I think is interesting to know how to rollback a commit. I'm used to just
 add a new commit removing the changes. That way we keep the history (made a
 mistake, fixed the mistake)

 Also, What we couldn't find out is how to delete a branch (or at least close
 it)

 Regards,
 Federico Ramallo
 -- next part --
 An HTML attachment was scrubbed...
 URL:
 http://lists.fossil-scm.org:8080/pipermail/fossil-users/attachments/20110312/98a2d4ec/attachment-0001.htm

 --

 Message: 2
 Date: Sat, 12 Mar 2011 17:27:45 +0100
 From: Joerg Sonnenberger jo...@britannica.bec.de
 Subject: Re: [fossil-users] git equivalent commands
 To: fossil-users@lists.fossil-scm.org
 Message-ID: 20110312162745.ga...@britannica.bec.de
 Content-Type: text/plain; charset=us-ascii

 On Sat, Mar 12, 2011 at 09:57:25AM -0600, Federico Ramallo wrote:
 Also, What we couldn't find out is how to delete a branch (or at least
 close
 it)

 Use the web ui. You can mark a branch leaf as closed and you can also
 move commits to different branches / change the tags etc.

 Joerg


 --

 Message: 3
 Date: Sat, 12 Mar 2011 10:29:25 -0600
 From: Federico Ramallo frama...@gmail.com
 Subject: Re: [fossil-users] git equivalent commands
 To: fossil-users@lists.fossil-scm.org
 Message-ID:
   aanlktimapzy21ankkkpitrnga2yzse1ecrgm2fdes...@mail.gmail.com
 Content-Type: text/plain; charset=iso-8859-1

 Awesome! I'll check it out! :D


 2011/3/12 Joerg Sonnenberger jo...@britannica.bec.de

 On Sat, Mar 12, 2011 at 09:57:25AM -0600, Federico Ramallo wrote:
  Also, What we couldn't find out is how to delete a branch (or at least
 close
  it)

 Use the web ui. You can mark a branch leaf as closed and you can also
 move commits to different branches / change the tags etc.

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

 -- next part --
 An HTML

Re: [fossil-users] Multiple Repos: single sign on

2011-03-12 Thread Nathaniel R. Reindl
On Tue, Mar 8, 2011 at 2:29 PM, Ron Wilson ronw.m...@gmail.com wrote:
 I think the best way is to set up Fossil to run as a CGI under a
 webserver and let the webserver take care of authentication of user
 ids. If you do this, you should set up the webserver to require HTTPS
 seesions because even HTTP Hash Authentication is weakly secure.

The only problem with this is that an HTTP client will implement
internal session handling inconsistently from another HTTP client.
The implication of this is that, while you can log in using basic or
digest HTTP authentication -- whether over SSL or otherwise -- you
lack the ability to log out.

That's just as much a security point in itself as the method by which
information is transmitted between two parties.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users