Re: [sqlite] How do I Register on sqlite.org

2005-03-18 Thread Kurt Welgehausen
You can record the ticket number when you originate the ticket and check the status any time with . Or, just bookmark the url after you submit the ticket. Or, you can scan (search) the timeline for the ticket number to see what action has been

Re: [sqlite] How do I Register on sqlite.org

2005-03-18 Thread Lawrence Chitty
David Wheeler wrote: On Mar 18, 2005, at 1:31 PM, Witold Czarnecki wrote: You don't need to register. Just place the ticket: http://www.sqlite.org/cvstrac/tktnew I did that before, but then I received no notifications when the ticket was updated or resolved. I'd love to get that information in

Re: [sqlite] How do I Register on sqlite.org

2005-03-18 Thread Derrell . Lipman
David Wheeler <[EMAIL PROTECTED]> writes: > On Mar 18, 2005, at 1:31 PM, Witold Czarnecki wrote: > >> You don't need to register. Just place the ticket: >> http://www.sqlite.org/cvstrac/tktnew > > I did that before, but then I received no notifications when the ticket was > updated or resolved.

Re: [sqlite] How do I Register on sqlite.org

2005-03-18 Thread David Wheeler
On Mar 18, 2005, at 1:31 PM, Witold Czarnecki wrote: You don't need to register. Just place the ticket: http://www.sqlite.org/cvstrac/tktnew I did that before, but then I received no notifications when the ticket was updated or resolved. I'd love to get that information in the future...

Re: [sqlite] How do I Register on sqlite.org

2005-03-18 Thread Witold Czarnecki
You don't need to register. Just place the ticket: http://www.sqlite.org/cvstrac/tktnew Best regards, Witold - Original Message - From: "David Wheeler" <[EMAIL PROTECTED]> To: "SQLite Users" <sqlite-users@sqlite.org> Sent: Friday, March 18, 2005 9:

[sqlite] How do I Register on sqlite.org

2005-03-18 Thread David Wheeler
Hi All, I'd like to file a bug report for SQLite, but do it as myself, so that I (hopefully) will receive emails whenever the ticket is updated. (I recently encountered a bug when I upgraded to 3.1.x, and then discovered that it wasn't a bug, but a bug fix--for a bug report I had filed!)