From: Simon Horman <horms@verge.net.au>
To: Graeme Fowler <graeme@graemef.net>
Cc: lvs-devel@vger.kernel.org
Subject: Re: Bugzilla
Date: Sat, 14 Feb 2009 09:15:43 +1100 [thread overview]
Message-ID: <20090213221543.GD11970@verge.net.au> (raw)
In-Reply-To: <1234530646.27072.7.camel@ernie.internal.graemef.net>
On Fri, Feb 13, 2009 at 01:10:46PM +0000, Graeme Fowler wrote:
> Guys
>
> Is it time, do you think, that we started using something like Bugzilla
> or Trac to keep, erm, track of coding changes, issues and/or bugs as
> they arise?
>
> I'm happy to host an instance of something if it helps.
In terms of managing patches, patchwork seems to be the new and
exciting tool to use. But in terms of managing bugs, tasks and the like,
I'm happy to work with whatever makes life easier for you, Joe, Malcolm
and the other people feilding lots questions on lvs-users.
--
Simon Horman
VA Linux Systems Japan K.K., Sydney, Australia Satellite Office
H: www.vergenet.net/~horms/ W: www.valinux.co.jp/en
next prev parent reply other threads:[~2009-02-13 22:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 13:10 Bugzilla Graeme Fowler
2009-02-13 22:15 ` Simon Horman [this message]
2009-02-14 9:49 ` Bugzilla Graeme Fowler
2009-02-15 15:08 ` Bugzilla Graeme Fowler
2009-02-15 22:18 ` Bugzilla Simon Horman
-- strict thread matches above, loose matches on Subject: below --
2008-04-29 10:53 Bugzilla Philip Balister
2008-04-29 12:00 ` Bugzilla Leon Woestenberg
2008-04-29 17:30 ` Bugzilla Rolf Leggewie
2005-05-19 6:25 Bugzilla Jean Delvare
2005-05-19 6:25 ` Bugzilla Philip Edelbrock
2005-05-19 6:25 ` Bugzilla Axel Thimm
2005-05-19 6:25 ` Bugzilla Jean Delvare
2005-05-19 6:25 ` Bugzilla Axel Thimm
2005-05-19 6:25 ` Bugzilla Jean Delvare
2005-05-19 6:25 ` Bugzilla Jean Delvare
2005-05-19 6:25 ` Bugzilla Axel Thimm
[not found] <1042750169.686.6.camel@tux.rsn.bth.se>
[not found] ` <1042752014.688.12.camel@tux.rsn.bth.se>
2003-01-16 23:50 ` bugzilla Harald Welte
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090213221543.GD11970@verge.net.au \
--to=horms@verge.net.au \
--cc=graeme@graemef.net \
--cc=lvs-devel@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.