public inbox for
 help / color / mirror / Atom feed
From: Chad Walstrom <>
To: Mel Hatzis <>
Subject: Re: code cleanup for release 4.1
Date: Sun, 01 Aug 2004 15:04:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]

Looks like I screwed up and didn't approve your post to help-gnats.  I'm
trying to bounce it there now, but Mailman may recognize duplicate
Message-Id and quell it.  I'll forward it instead if it doesn't go

Mel Hatzis wrote:
> Chad, as part of the code cleanup for release 4.1, I'd like to
> contribute some function name changes and subtle code re-organization
> in preparation for the gnats-dbi integration (which I think we're
> going to fold into Gnats 5.0).
> Let me know if you find this acceptable (or not). I think that
> providing these patches in small chunks will make the whole dbi
> project a lot easier to swallow and digest.

Sounds like a good plan to me.  I'm not certain if you prefer to submit
patches for me to roll in, or if you want to use branching on the CVS
repository for savannah.  I'm open to either.

Chad Walstrom <> 
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

Help-gnats mailing list

  parent reply	other threads:[~2004-08-01 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-01 13:53 Mel Hatzis
2004-08-01 14:40 ` Mel Hatzis
2004-08-01 15:04 ` Chad Walstrom [this message]
     [not found] ` <>
     [not found]   ` <>
2005-02-18 19:56     ` Chad Walstrom

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:

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

  git send-email \ \ \ \ \

* 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).