Re: [fossil-users] Automatic Ticket-commit tagging

Steve's summary is as close to accurate as i could have put it. The config stuff is not stored in permanent artifacts, and can synced but does not participate in merging and whatnot. Anything UI-independent of potential historical significance is stored in an artifact. - stephan Sent from a

Re: [fossil-users] Automatic Ticket-commit tagging

On Mon, May 23, 2016 at 10:41 AM, Steve Schow wrote: > Is it fair to say, tickets, wikis and checkins are stored in artifacts…. > while pretty much all configuration stuff including TH1 code, SQL, UI > enhancements, etc are probably not artifacted? > I don't know if they are

Re: [fossil-users] Automatic Ticket-commit tagging

On Sun, May 22, 2016 at 4:42 PM, Steve Schow wrote: > > with regards to this statement… > > On May 22, 2016, at 1:40 PM, Ron W wrote: > > > Everything in Fossil is stored in artifacts. > > Are ticket reports stored as versioned artifacts? I should revise

Re: [fossil-users] Automatic Ticket-commit tagging

Can you please show me where I can find version history of the ticket report SQL statement? I have been copy and pasting this into a text file in order to get versioning on it…but if fossil is versioning it already then I don’t need to, but I was not able to see any way to do that. On May

Re: [fossil-users] Automatic Ticket-commit tagging

On 5/22/2016 3:53 PM, Steve Schow wrote: > I’m sorry I’m not seeing anywhere that ticket “reports” are contained as > versioned artifacts… Ticket reports are formatted the same as changes. -- Andy Goth | signature.asc Description: OpenPGP digital signature

Re: [fossil-users] Automatic Ticket-commit tagging

I’m sorry I’m not seeing anywhere that ticket “reports” are contained as versioned artifacts… On May 22, 2016, at 2:50 PM, Andy Goth wrote: > On 5/22/2016 3:42 PM, Steve Schow wrote: >> On May 22, 2016, at 1:40 PM, Ron W wrote: >>> Everything in

Re: [fossil-users] Automatic Ticket-commit tagging

On 5/22/2016 3:42 PM, Steve Schow wrote: > On May 22, 2016, at 1:40 PM, Ron W wrote: >> Everything in Fossil is stored in artifacts. > > Are ticket reports stored as versioned artifacts? http://fossil-scm.org/index.html/doc/trunk/www/fileformat.wiki#tktchng -- Andy Goth

Re: [fossil-users] Automatic Ticket-commit tagging

with regards to this statement… On May 22, 2016, at 1:40 PM, Ron W wrote: > Everything in Fossil is stored in artifacts. Are ticket reports stored as versioned artifacts? ___ fossil-users mailing list

Re: [fossil-users] Automatic Ticket-commit tagging

ok, but the ticket table does not contain artifacts. It was not obvious to me that tickets are under version control in another place. It is now. On May 22, 2016, at 1:40 PM, Ron W wrote: > On Sat, May 21, 2016 at 4:36 PM, Steve Schow wrote: > Thanks

Re: [fossil-users] Automatic Ticket-commit tagging

On Sat, May 21, 2016 at 4:36 PM, Steve Schow wrote: > Thanks for that information. I was not aware that ticket changes involved > artifacts also. > Everything in Fossil is stored in artifacts. The DB serves as artifact storage, indexing of artifacts and a convenient cache of

Re: [fossil-users] Automatic Ticket-commit tagging

Thanks for that information. I was not aware that ticket changes involved artifacts also. I should have known that, but I’m still getting up to speed with fossil. A few months back when I first started using fossil I batch changed a bunch of tickets using SQL, I changed the value of the

Re: [fossil-users] Automatic Ticket-commit tagging

On Fri, May 20, 2016 at 10:43 AM, Steve Schow wrote: > I think perhaps you meant “commit” comment below? Its the commit comment > that needs to be tweaked, in theory, by the TH1…not the ticket itself. So > are you saying that modifying a commit comment requires that an

Re: [fossil-users] Automatic Ticket-commit tagging

I think perhaps you meant “commit” comment below? Its the commit comment that needs to be tweaked, in theory, by the TH1…not the ticket itself. So are you saying that modifying a commit comment requires that an artifact be created with TH1 somehow, if even possible? For the ticket table, I

Re: [fossil-users] Automatic Ticket-commit tagging

On Fri, May 20, 2016 at 2:21 AM, Steve Schow wrote: > Hmm, very interesting idea about using the EDITOR feature to run a > pre-script…i will have to ponder that…possibly an alternative to using an > actual wrapper script…. > > Sounds like server side TH1 probably won’t do it. >

Re: [fossil-users] Automatic Ticket-commit tagging

Hmm, very interesting idea about using the EDITOR feature to run a pre-script…i will have to ponder that…possibly an alternative to using an actual wrapper script…. Sounds like server side TH1 probably won’t do it. throwing a table into the checkout DB would be easy enough to do…can use sqlite

Re: [fossil-users] Automatic Ticket-commit tagging

On Wed, May 18, 2016 at 2:12 PM, Steve Schow wrote: > > I’m going to try to make some kind of wrapper script to my commit command > that can do this for me, but before I embark I am wondering if anyone has > thought of any good ways to do this, perhaps using TH1 in the repo or >

[fossil-users] Automatic Ticket-commit tagging

I am getting tired of having to copy and paste the ticket uid into my commit comments in order to automatically link multiple commits to a single ticket. The ability to go to a ticket and see the list of checkins associate with it is very important to me, but the manual overhead to make it so,