1GIT-SEND-BUGZILLA(1)            [FIXME: manual]           GIT-SEND-BUGZILLA(1)
2
3
4

NAME

6       git-send-bugzilla - Attach patches to a bugzilla bug
7

SYNOPSIS

9       git-send-bugzilla [OPTIONS] (--dry-run | <bugid>)
10                           <since>[..<until>]
11

DESCRIPTION

13       Attach each commit between <since> and <until> to the bug <bugid> on
14       GNOME’s bugzilla. If ..<until> is not specified, the head of the
15       current working tree is implied.
16
17       If -n (or bugzilla.numbered in the repository configuration) is
18       specified, instead of "[PATCH] Subject", the first line is formatted as
19       "[n/m] Subject".
20

OPTIONS

22       -b|--url <url>
23           The Bugzilla URL.
24
25       -u|--username <username>
26           Your Bugzilla user name.
27
28       -p|--password <password>
29           Your Bugzilla password.
30
31       -s|--squash
32           Send all the selected commits as a single patch.
33
34       -n|--numbered
35           Prefix attachment names with [n/m].
36
37       --start-number <n>
38           Start numbering the patches at <n> instead of 1.
39
40       --dry-run
41           Don’t do anything for real. If you use this option you shouldn’t
42           specify a bug id.
43

CONFIGURATION

45       You can specify an URL, an user name and a password for the bugzilla in
46       the repository configuration as follows:
47
48
49           [bugzilla]
50                   url = "http://bugzilla.kernel.org"
51                   username = "wanda@gnome.org"
52                   password = "********"
53
54       If you don’t specify one of them in the repository configuration nor in
55       the command line, git-send-bugzilla will ask for it before trying to
56       attach the patches.
57

EXAMPLES

59       git-send-bugzilla -n 12345 master Extract all commits which are in the
60       current branch but not in the master branch. Each commit will be
61       attached as a single patch to the bug #12345
62

AUTHOR

64       Written by Steve Frécinaux <code@istique.net[1]>.
65

DOCUMENTATION

67       Documentation by Steve Frécinaux <code@istique.net[1]>.
68

NOTES

70        1. code@istique.net
71           mailto:code@istique.net
72
73
74
75[FIXME: source]                   02/21/2010              GIT-SEND-BUGZILLA(1)
Impressum