From: "Flammie Pirinen" <flammie@lark.gentoo.org>
To: gentoo-doc-cvs@lists.gentoo.org
Subject: [gentoo-doc-cvs] cvs commit: ebuild-submit.xml
Date: Mon, 24 Oct 2005 13:29:47 +0000 [thread overview]
Message-ID: <200510241330.j9ODTxOS022112@robin.gentoo.org> (raw)
flammie 05/10/24 13:29:47
Modified: xml/htdocs/doc/en ebuild-submit.xml
Log:
Bug #110314: Bug reporter doesn't need to be in CC when using bugzilla's
default mail settigns.
Revision Changes Path
1.12 +6 -6 xml/htdocs/doc/en/ebuild-submit.xml
file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/ebuild-submit.xml?rev=1.12&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/ebuild-submit.xml?rev=1.12&content-type=text/plain&cvsroot=gentoo
diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/ebuild-submit.xml.diff?r1=1.11&r2=1.12&cvsroot=gentoo
Index: ebuild-submit.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/ebuild-submit.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -r1.11 -r1.12
--- ebuild-submit.xml 2 Jul 2005 09:59:44 -0000 1.11
+++ ebuild-submit.xml 24 Oct 2005 13:29:47 -0000 1.12
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ebuild-submit.xml,v 1.11 2005/07/02 09:59:44 swift Exp $ -->
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/ebuild-submit.xml,v 1.12 2005/10/24 13:29:47 flammie Exp $ -->
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
<guide link = "/doc/en/ebuild-submit.xml">
@@ -13,8 +13,8 @@
tracking system.
</abstract>
-<version>1.4</version>
-<date>2005-07-02</date>
+<version>1.5</version>
+<date>2005-10-24</date>
<chapter>
<title>Getting Started</title>
@@ -115,9 +115,9 @@
</p>
<p>
-Leave the <c>Assigned To</c> field blank, but if you'd like
-to track the status of your ebuild, enter your email in the
-<c>CC</c> field.
+Leave the <c>Assigned To</c> field blank. If you haven't changed
+Bugzilla's mail settings, you, as a reporter, will automatically
+receive email on bug updates.
</p>
<p>
--
gentoo-doc-cvs@gentoo.org mailing list
next reply other threads:[~2005-10-24 13:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 13:29 Flammie Pirinen [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-16 3:04 [gentoo-doc-cvs] cvs commit: ebuild-submit.xml Josh Saddler
2008-05-20 18:45 Sven Vermeulen
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=200510241330.j9ODTxOS022112@robin.gentoo.org \
--to=flammie@lark.gentoo.org \
--cc=docs-team@lists.gentoo.org \
--cc=gentoo-doc-cvs@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox