> Tracking Line-wise File History
>
> Does the version control system have an option to track the
> history of the file line-by-line? I.e., can it show for each
> line at which revision it was most recently changed, and by
> whom?
This is available from the web interface, under file history. Each
I have to say I'd love to see this skin incorporated, very nice work.
-Original Message-
From: "Richard Hipp"
Sent: Monday, June 21, 2010 11:01am
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] A lightweight plain skin for Fossil: Plain Wedding
_
Hi James,
If you want events along with usernames, you could query the Fossil repo.
select * from event where type='ci' and user!='' order by mtime;
Filling in the user field, you could exclude yourself.
-Original Message-
From: "James Bremner"
Sent: Monday, May 31, 2010 5:37pm
To: f
This will prove useful here at work, thank you for creating this.
-Original Message-
From: "Michael McDaniel"
Sent: Saturday, May 29, 2010 10:50am
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] Fossil for dummies PDF
On Sat, May 29, 2010 at 06:20:01AM -0400, Jim Schimp
I am thinking about taking a stab at implementing an ignore-list feature
similar to git's .gitignore to prevent pesky and unwanted files from making it
into commits. If this feature already exists in Fossil I have overlooked it.
My initial plan is to have a list of patterns contained within a
Hey,
Thanks for the link. I eventually came around to the same technique in ddd,
putting a sleep call in the function that the child executes, using ps to find
the parent process id, and then attaching to the child with ddd.
___
fossil-users mailin
A non-terminated char array was printing garbage in the "attachview" page.
--- ../../fossil-src-20100318142033/src/info.c 2010-03-18 10:20:53.0
-0400
+++ info.c 2010-05-21 10:45:25.907388684 -0400
@@ -753,8 +753,9 @@ static void object_description(
@ Attachment "%h(zFilename)
Hello All,
This patch adds a complete seach mechanism for wikis, tickets, checkins, and
code. This functionality is only available if you are logged in.
diff -rup ../fossil-src-20100318142033/src/db.c ./src/db.c
--- ../fossil-src-20100318142033/src/db.c 2010-03-18 10:20:53.0
-0
I'm making a first pass at implementing code/tickets/wiki search. Anybody
working on something similar? If you have any thoughts on functionality,
implementation, or anything else, let me know.
diff -rupN fossil_src_orig/src/db.c fossil2/src/db.c
--- fossil_src_orig/src/db.c2010-03-18 10
I have introduced a new capability 'q', or "assign ticket". It is not a
default out of the box, but can easily be added to groups or individuals as
needed. This is in addition to the "my tickets" report that is now displayed
as part of the ticket reports page.
diff -rupN fossil_src_orig/src
round with this to see what feels right.
If anyone has further suggestions on the look/feel, or implementation, please
let me know.
-Original Message-
From: "Joshua Paine"
Sent: Thursday, May 13, 2010 11:11am
To: fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-user
I have added some additional features to ticket assignment. Administrators may
assign on ticket creation/editing. Normal developers may now assign and
unassign themselves without any special privileges. Viewing who has what
ticket and self assigning/unassigning is done right in the "all ticke
I don't understand how the fossil web server is interacting with the child
processes that it launches. I see the code in cgi.c that does the launching,
but I don't see how the child processes actually know what it is they should be
doing.
if( select( listener+1, &readfds, 0, 0, &delay) ){
I have continued work on ticket assignment. Tickets can now be assigned by
administrators. Users have a "My Tickets" report, and an Assigned column now
exists in the ticket listings. I would like to give users the ability to assign
and unassign themselves. What does everybody think?
diff -ru
I have developed a simple patch to introduce ticket assignment. I have yet to
add an "assigned to" column in all places that may be necessary. Is this
something people would be interested in seeing included with the standard
fossil distribution?
diff -rupN fossil_src_orig/src/schema.c fossil_
15 matches
Mail list logo
