From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pete Phillips Subject: Re: Bug Tracker? Date: Tue, 22 Apr 2008 10:04:09 +0100 Message-ID: <7658.1208855049@localhost> References: Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JoEQd-0000yy-IC for emacs-orgmode@gnu.org; Tue, 22 Apr 2008 05:04:43 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JoEQb-0000xR-Gq for emacs-orgmode@gnu.org; Tue, 22 Apr 2008 05:04:42 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JoEQa-0000x4-W2 for emacs-orgmode@gnu.org; Tue, 22 Apr 2008 05:04:41 -0400 Received: from mailhost.smtl.co.uk ([193.131.77.174]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JoEQZ-0003Ur-FH for emacs-orgmode@gnu.org; Tue, 22 Apr 2008 05:04:40 -0400 In-reply-to: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Jeff Mickey Cc: emacs-orgmode Hi Jeff >>>>> "Jeff" == Jeff Mickey writes: Jeff> I was wondering if anyone uses Org-Mode to track bugs in their Jeff> software, and if there were any nifty things you did to make Jeff> it work a bit smoother. I'd like to have a /bugs.org or Jeff> /issues.org at the top of my source tree, and track bugs there Jeff> with org-mode. Any suggestions on the best practices for Jeff> this? Well not exactly bug tracking, but we have recently started using an org-mode file as our System log for our IT stuff in conjunction with git. I've attached a snippet of the file. We set up a git repo on one of our internal file servers, and then by pulling it to our laptops we can work on the log, and then push it back to the file server on a regular basis. git takes care of syncing everything for us (well, works so far). Also, that means if the server crashes at least one of us will have the most recent entry on a laptop. Top level headers = months, ** = the date, and then *** = each problem we deal with on that date. we use tags to note who made the entry. Pretty sure you could use something similar for bugs. Pete #+TAGS: #+TAGS: pete(p) jonny(j) #+TITLE: SMTL Sys Admin Log - 2008 #+INFOJS_OPT: view:info * Jan ** [2008-01-22 Tue] *** xxx xxxx unable to access intranet Asked xx to ssh to xxx.xxx.xx.xxx, success this indicates that it's not a firewall or ssh issue. I suspect its a DNS issue, asked xx for the output of cat /etc/hosts and echo $SHELL the latter to get socks info if in login script, hosts file returned no output asked Jo to stat the file it returned empty. Found a filed copy of xx's hosts file asked her to amend this to /etc/hosts. Intranet access returned. *** Issue with tiger scripts kept getting emails: : From: root@smtl.co.uk (Cron Daemon) : To: root@smtl.co.uk : Subject: Cron test -x /usr/sbin/tigercron && /usr/sbin/tigercron -q : Configured working directory /var/run/tiger/work does not exist Fixed (i hope) by adding: : # need to make this directory for tiger to run : # PJP Wed Apr 2 13:19:58 BST 2008 pete@smtl.co.uk : mkdir -p /var/run/tiger/work/ to /etc/rc.local