From: "Steve Frécinaux" <nudrema@gmail•com>
To: git@vger•kernel.org
Subject: git-bugzilla
Date: Sun, 16 Nov 2008 22:00:26 +0100 [thread overview]
Message-ID: <492089EA.60205@gmail.com> (raw)
Hi folks,
Here is a chunk of code I wrote a few time ago, to post patches to
bugzilla, modelled mostly after git-format-patch/git-send-email.
You can find it there:
http://code.istique.net/?p=git-bugzilla.git
It is written in perl and requires WWW::Mechanize.
Hope you like it.
Here is an excerpt of the man page:
NAME
----
git-send-bugzilla - Attach patches to a bugzilla bug
SYNOPSIS
--------
'git-send-bugzilla' [OPTIONS] (--dry-run | <bugid>)
<since>[..<until>]
DESCRIPTION
-----------
Attach each commit between <since> and <until> to the bug <bugid>
on GNOME's bugzilla.
If ..<until> is not specified, the head of the current working
tree is implied.
If -n (or bugzilla.numbered in the repository configuration) is
specified, instead of "[PATCH] Subject", the first line is
formatted as "[n/m] Subject".
OPTIONS
-------
-b|--url <url>::
The Bugzilla URL.
-u|--username <username>::
Your Bugzilla user name.
-p|--password <password>::
Your Bugzilla password.
-s|--squash::
Send all the selected commits as a single patch.
-n|--numbered::
Prefix attachment names with [n/m].
--start-number <n>::
Start numbering the patches at <n> instead of 1.
--dry-run::
Don't do anything for real. If you use this option you
shouldn't specify a bug id.
EXAMPLES
--------
git-send-bugzilla -n 12345 master
Extract all commits which are in the current branch but
not in the 'master' branch. Each commit will be attached as
a single patch to the bug #12345
next reply other threads:[~2008-11-16 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 21:00 Steve Frécinaux [this message]
2008-11-17 1:23 ` git-bugzilla Jakub Narebski
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=492089EA.60205@gmail.com \
--to=nudrema@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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