Your message dated Sat, 5 Feb 2005 01:34:51 +0100
with message-id <[EMAIL PROTECTED]>
and subject line maint-guide is not dictionary nor FAQ :-)
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 6 Dec 2001 14:30:26 +0000
>From [EMAIL PROTECTED] Thu Dec 06 08:30:25 2001
Return-path: <[EMAIL PROTECTED]>
Received: from smtp01.mrf.mail.rcn.net [207.172.4.60]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 16BzXd-0003qk-00; Thu, 06 Dec 2001 08:30:25 -0600
Received: from 146-115-121-200.c3-0.smr-ubr1.sbo-smr.ma.cable.rcn.com
([146.115.121.200] helo=mizar.alcor.net)
by smtp01.mrf.mail.rcn.net with esmtp (Exim 3.33 #10)
id 16BzXd-0006xe-00
for [EMAIL PROTECTED]; Thu, 06 Dec 2001 09:30:25 -0500
Received: from mdz by mizar.alcor.net with local (Exim 3.33 #1 (Debian))
id 16BzXc-0007cQ-00
for <[EMAIL PROTECTED]>; Thu, 06 Dec 2001 09:30:24 -0500
Date: Thu, 6 Dec 2001 09:30:24 -0500
From: Matt Zimmerman <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Include definitions for common Debian acronyms
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.3.23i
X-Debbugs-CC: [email protected]
Sender: Matt Zimmerman <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Package: maint-guide
Severity: wishlist
(maint-guide maintainer: it would be nice if the New Maintainer's Guide
included the expansions of these acronyms)
On Thu, Dec 06, 2001 at 09:10:49AM -0500, Mark Bucciarelli wrote:
> Greetings, all. I've been lurking on this list for about a month and
> following Debian news closely over the same period. I have a small
> opensource project, written in Java, and I would like toc reate debs for
> it.
>
> One thing I have found challenging is the number of acronyms debian folks
> use, both on this list and in news releases. Could someone please define
> the following:
>
> NMU
Non-Maintainer Upload. Refer to the Developer's Reference:
http://www.debian.org/doc/developers-reference/
In fact, read the whole thing. It has lots of information that you should
know.
> ITP
Intent to Package. See http://www.debian.org/devel/wnpp/
> RC
Release-Critical. Refers to a bug which must be fixed before a package is
suitable for release.
> BTS
Bug Tracking System. See bugs.debian.org.
--
- mdz
---------------------------------------
Received: (at 122699-done) by bugs.debian.org; 5 Feb 2005 00:31:57 +0000
>From [EMAIL PROTECTED] Fri Feb 04 16:31:57 2005
Return-path: <[EMAIL PROTECTED]>
Received: from outmx007.isp.belgacom.be [195.238.3.234]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CxDrg-0003Om-00; Fri, 04 Feb 2005 16:31:57 -0800
Received: from outmx007.isp.belgacom.be (localhost [127.0.0.1])
by outmx007.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
ESMTP id j150VmQ0020407
for <[EMAIL PROTECTED]>; Sat, 5 Feb 2005 01:31:48 +0100
(envelope-from <[EMAIL PROTECTED]>)
Received: from dambo.lan.aokiconsulting.com (183.81-201-80.adsl.skynet.be
[80.201.81.183])
by outmx007.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
ESMTP id j150Vh26020374;
Sat, 5 Feb 2005 01:31:43 +0100
(envelope-from <[EMAIL PROTECTED]>)
Received: from osamu by dambo.lan.aokiconsulting.com with local (Exim 4.44)
id 1CxDuW-0001aX-0C; Sat, 05 Feb 2005 01:34:52 +0100
Date: Sat, 5 Feb 2005 01:34:51 +0100
From: Osamu Aoki <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: Joe Oppegaard <[EMAIL PROTECTED]>, [email protected]
Subject: maint-guide is not dictionary nor FAQ :-)
Message-ID: <[EMAIL PROTECTED]>
Mail-Followup-To: [EMAIL PROTECTED],
Joe Oppegaard <[EMAIL PROTECTED]>, [email protected]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-GPG-Fingerprint: 253A 4076 6A3B CCE2 A426 DEF5 E80F C4C1 A806 1F32
User-Agent: Mutt/1.5.6+20040907i
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
ITP, NMU, RC, BTS ... add tyhese to dictionary :-)
I actually like your idea of mentioning NM related acronym.
But specific application process related things such as ITP are not the
focus of current maint-guide, writing unmaintainable contents into this
may be a bloat. But rest assured, I now have pointer to mpalmer's The
debian-mentors FAQ in Chapter 10.
This captures most of confusion if NM read it. Also BTS and NM URLs are
also in Chapter 10. Since now this has guide for pbuilder and I mention
FTBFS anf RC there, that should be OK.
NMU versioning may be for NM test. In this document, we talk only
simple packaging. So keep this in developer-reference as now. NM has
to read it anyway. Pointer to developer-reference exists in Chapter 1.
There we have NMU mentioned.
With all these your concern is mostly covered, I hope.
There is another dictionary project which want to capture these Debian
jargons and make printable and dict command compatible dictionary. So
let's keep fun to them. (CCing to the proposer and debian-doc list)
So from maint-guide BTS, let me erase this.
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <[EMAIL PROTECTED]> Brussels Belgium, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
