From: Christian Faulhammer <fauli@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: rfc: pybugz option conflict
Date: Mon, 11 May 2009 22:17:00 +0200 [thread overview]
Message-ID: <20090511221700.73d650bf@gentoo.org> (raw)
In-Reply-To: <20090511160124.GA31551@linux1>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
William Hubbs <williamh@gentoo.org>:
> optparse wants to use --version to display the version of the program,
> and we are using --version in the post command to set the version that
> will be part of the bug. What do you think we could use for --version
> in the post command instead so that we can use --version to display
> the program version?
--bugzilla-version --bugversion
V-Li
- --
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode
<URL:http://gentoo.faulhammer.org/>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)
iEYEARECAAYFAkoIh7wACgkQNQqtfCuFneMpWQCeK0gayJElyJHL4e4WMK6vhhth
a8MAn2wKryzV6wbZNwdYosZX++W/F2ZL
=F7dh
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2009-05-11 20:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 16:01 [gentoo-dev] rfc: pybugz option conflict William Hubbs
2009-05-11 20:17 ` Christian Faulhammer [this message]
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=20090511221700.73d650bf@gentoo.org \
--to=fauli@gentoo.org \
--cc=gentoo-dev@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