Re: [fossil-users] Fossil vs. GitHub

2017-12-14 Thread Ron W 
On Thu, Dec 14, 2017 at 7:00 AM, <fossil-users-requ...@lists.fossil-scm.org>
wrote:
>
> Date: Wed, 13 Dec 2017 18:04:41 -0600 (CST)
> From: Roy Keene <fos...@rkeene.org>
> Subject: Re: [fossil-users] Fossil vs. GitHub
>
> One thing I often wish Fossil did was show other things (tickets, wiki
> pages) that reference tickets rather than just checkins -- I often have a
> mess of tickets that refer to other tickets and no place to generate a
> list of them, or reverse them.


I'm not sure how the TH1 regexp command works, but it might be possible to
at least find other tickets that reference a specific ticket using a
combination of SQL in Fossil's ticket report subsystem and TH1+SQL in the
new and edit ticket scripts in the ticket configuration.

In the ticket configuration, add a new table to the ticket schema to that
has 2 columns: "referree" and "referrer"..

In the new and edit ticket TH1 scripts, enhance the submit handling to find
artifact references using the regexp command with the regex "\[[0-9a-f]\]".
For each match, add (or update) a row to the new table with referree = ID
found and referrer = ID of current ticket.

Of course, this assumes that the ticket TH1 scripts can access the ID of
the current ticket and that the TH1 regexp command can be used to get a
list of locations of regex matches.

Maybe some Javascript can extract the ticket ID from the URL and supply
that as a hidden field back to the TH1 scripts.

If regexp doesn't work as needed, may be possible to use "string first" and
"string range" to find and extract artifact IDs.

As for wiki pages, maybe the "webpage_notify" hook can be used to find
artifact references.
___
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. GitHub

2017-12-13 Thread Roy Keene 
One thing I often wish Fossil did was show other things (tickets, wiki 
pages) that reference tickets rather than just checkins -- I often have a 
mess of tickets that refer to other tickets and no place to generate a 
list of them, or reverse them.


On Wed, 13 Dec 2017, Richard Hipp wrote:


On 12/13/17, jungle Boogie  wrote:

On 13 December 2017 at 09:07, Warren Young  wrote:

On Dec 13, 2017, at 9:55 AM, Richard Hipp  wrote:


Would Git or GitHub have told me about those prior tickets?


GitHub is pretty good about surfacing such information, as long as the
ticket references the checkin ID.


Yep. With most projects I follow on github, the commiter includes the
referenced issue number in the description or somewhere in the commit
message.


Is the ticket number included in the check-in that *fixed* the issue,
or in the check-in that *caused* the issue.  Therein lays the
difference.  I wasn't looking that one of the check-ins that fixed the
bug - I was looking at the check-in that caused the bug, and it
referred me forward to issues that happened in the future.

Maybe GitHub will do that?  Do you have an example?
--
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] Fossil vs. GitHub

2017-12-13 Thread Richard Hipp 
On 12/13/17, jungle Boogie  wrote:
> On 13 December 2017 at 09:07, Warren Young  wrote:
>> On Dec 13, 2017, at 9:55 AM, Richard Hipp  wrote:
>>>
>>> Would Git or GitHub have told me about those prior tickets?
>>
>> GitHub is pretty good about surfacing such information, as long as the
>> ticket references the checkin ID.
>
> Yep. With most projects I follow on github, the commiter includes the
> referenced issue number in the description or somewhere in the commit
> message.

Is the ticket number included in the check-in that *fixed* the issue,
or in the check-in that *caused* the issue.  Therein lays the
difference.  I wasn't looking that one of the check-ins that fixed the
bug - I was looking at the check-in that caused the bug, and it
referred me forward to issues that happened in the future.

Maybe GitHub will do that?  Do you have an example?
-- 
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 vs. GitHub

2017-12-13 Thread jungle Boogie 
On 13 December 2017 at 09:07, Warren Young  wrote:
> On Dec 13, 2017, at 9:55 AM, Richard Hipp  wrote:
>>
>> Would Git or GitHub have told me about those prior tickets?
>
> GitHub is pretty good about surfacing such information, as long as the ticket 
> references the checkin ID.

Yep. With most projects I follow on github, the commiter includes the
referenced issue number in the description or somewhere in the commit
message.

>
> In fact, GitHub can be a bit overeager about cross-linking everything.  Just 
> write “#1” in some bit of Markdown somewhere, and you’ll get linked to issue 
> #1, even if you didn’t mean to refer to it.
>

Agreeded.

> Git wouldn’t, of course, since it doesn’t have a ticket tracker. :)  
> Presumably there are Git + bug tracker lash-ups that will do this 
> bidirectional linking.
>

-- 
---
inum: 883510009027723
sip: jungleboo...@sip2sip.info
___
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. GitHub

2017-12-13 Thread Warren Young 
On Dec 13, 2017, at 9:55 AM, Richard Hipp  wrote:
> 
> Would Git or GitHub have told me about those prior tickets?

GitHub is pretty good about surfacing such information, as long as the ticket 
references the checkin ID.  

In fact, GitHub can be a bit overeager about cross-linking everything.  Just 
write “#1” in some bit of Markdown somewhere, and you’ll get linked to issue 
#1, even if you didn’t mean to refer to it.

Git wouldn’t, of course, since it doesn’t have a ticket tracker. :)  Presumably 
there are Git + bug tracker lash-ups that will do this bidirectional linking.

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

[fossil-users] Fossil vs. GitHub

2017-12-13 Thread Richard Hipp 
A bug was reported again SQLite, just moments ago.  Bisecting lands on
this check-in: https://www.sqlite.org/srcx/info/559733b09e

Right away, I see that there are two prior bug reports against the
same check-in, which seems like important information from a project
administrator perspective.  (I have since added a ticket for the new
bug so now there are three.).

Would Git or GitHub have told me about those prior tickets?

-- 
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