emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Pete Phillips <pete@smtl.co.uk>
To: Jeff Mickey <jeff@archlinux.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Bug Tracker?
Date: Tue, 22 Apr 2008 10:04:09 +0100	[thread overview]
Message-ID: <7658.1208855049@localhost> (raw)
In-Reply-To: <fbe757b30804211438q183707a0icdf3ab89c2b4a94f@mail.gmail.com>

Hi Jeff

>>>>> "Jeff" == Jeff Mickey <jeff@archlinux.org> 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 <root@xxxxxx>    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

  reply	other threads:[~2008-04-22  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21 21:38 Bug Tracker? Jeff Mickey
2008-04-22  9:04 ` Pete Phillips [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-05 19:51 Ken Mankoff
2018-11-05 20:55 ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7658.1208855049@localhost \
    --to=pete@smtl.co.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=jeff@archlinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).