unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: ghouston@arglist.com, mvo@zagadka.ping.de, guile-devel@gnu.org
Subject: Re: Tool version in HACKING
Date: Wed, 10 Apr 2002 10:07:42 -0500	[thread overview]
Message-ID: <87n0wbwq0x.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <E16vBc8-0006ne-00@giblet> (Thien-Thi Nguyen's message of "Tue, 09 Apr 2002 23:29:52 -0700")

Thien-Thi Nguyen <ttn@giblet.glug.org> writes:

> btw, in fixing this bug we come to the process question of: how do bugs
> fit into the TODO list?  one obvious answer is "don't use TODO list, bug
> fixing (for those deemed needing it) is best managed separately".  this
> is a not wholistic view however; bug fixing takes time which directly
> affects what can be done on TODO.  fundamentally, bug fixing is a (we
> hope) non-repetitive action, something to do when the time is right.
> (and if the particular fix is congruent w/ long term design, the fix
> could be called one-shot.)
>
> so i think it would be useful to consider ways to include bugs in the
> TODO list.  what does everyone think about this protocol:

I'm not sure I follow.  I can see why we might want to have references
to bugs from the TODO list; are you arguing for more than that?  (I
don't think I adequately grokked your suggestion).

Thanks

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-04-10 15:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-09 17:12 Tool version in HACKING Marius Vollmer
2002-04-09 19:28 ` Gary Houston
2002-04-10  6:29   ` Thien-Thi Nguyen
2002-04-10 15:07     ` Rob Browning [this message]
2002-04-10 18:42       ` Thien-Thi Nguyen
2002-04-22 16:59     ` Thien-Thi Nguyen
     [not found] ` <200204091928.MAA18084@onyx.he.net>
2002-04-15 13:59   ` Marius Vollmer

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.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=87n0wbwq0x.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=ghouston@arglist.com \
    --cc=guile-devel@gnu.org \
    --cc=mvo@zagadka.ping.de \
    /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 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).