git-bz - Bugzilla Subcommand for Git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add a ‘REPORTING BUGS’ section to the man page	Philip Withnall	2015-02-12	1	-0/+4
\| \| \| \| \| \|	So that people know where to report git-bz bugs. https://bugzilla.gnome.org/show_bug.cgi?id=742370
*	Retitle the ‘AUTHORS’ section in the man page	Philip Withnall	2015-02-12	1	-2/+2
\| \| \| \| \| \| \|	Title it ‘AUTHORS’ rather than ‘Author’ to make it more in line with other man pages. https://bugzilla.gnome.org/show_bug.cgi?id=742370
*	attach: Obsolete patches with the same subject	Jasper St. Pierre	2012-03-13	1	-0/+5
\| \| \| \| \| \| \| \| \|	For plain 'git bz attach', always obsolete existing patches if they have the same subject as the commit being attached. For 'git bz attach -e', make this the default. https://bugzilla.gnome.org/show_bug.cgi?id=671941
*	apply: attempt to handle plain diffs	Dan Winship	2012-03-01	1	-1/+3
\| \| \| \| \| \| \| \| \|	If a bug has a plain diff (as opposed to git-format-patch output), prepend some minimal headers to it to get it into a format git-am will accept, and then make the user write a commit message for it before proceeding. https://bugzilla.gnome.org/show_bug.cgi?id=657558
*	apply: add --continue/--skip/--abort	Dan Winship	2012-03-01	1	-1/+11
\| \| \| \| \| \| \| \| \| \| \|	Rather than failing completely when git-am fails to apply a patch, write out our current state to git-am's temporary directory, and then tell the user to use "git bz apply --continue/--skip/--abort" after handling the merge failure. When the user uses one of those options, read back our state, pass the flag on to git-am, and (assuming git-am succeeds), continue with the next patch. https://bugzilla.gnome.org/show_bug.cgi?id=657558
*	apply: add interactive option	Dan Winship	2012-03-01	1	-4/+7
\| \| \| \| \| \| \| \| \| \| \| \| \|	Rather than asking whether or not to apply each patch individually, list all of the patches at once and allow the user to either apply all of them, apply none of them, or interactively choose which ones to apply (a la interactive rebasing). In addition to choosing which patches to apply, the interactive option also allows reordering the patches before applying, and choosing to apply committed or rejected patches. https://bugzilla.gnome.org/show_bug.cgi?id=657558
*	Work around line-break problems	Owen W. Taylor	2012-03-01	1	-0/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	The two lines for the different versions of 'git bz edit' are treated by asciidoc as a single paragraph and line-wrapped. In theory, a + at the end of a line is a forced line-break with asciidoc, but in the manpage generation route, this doesn't work properly - the magic in a2x that is supposed to turn the asciidoc-br processing instruction into a line break doesn't work. (We aren't using a2x at the moment for the conversion, but no real reason to switch if it doesn't work better.) So, use a [verse] paragraph instead. This results in mis-indentation, but slightly better than the previous breakage. https://bugzilla.gnome.org/show_bug.cgi?id=670686
*	Allow setting bz.default-<field name>	Owen W. Taylor	2012-02-05	1	-7/+29
\| \| \| \| \| \| \| \| \| \| \|	If you want to override something like the default version on a per-component basis, having to set that in the per-tracker configuration is unnatural and confusing. Allow setting bz.default-version instead. This is interpreted as overriding the existing configuration of default field values. Based on a patch from Dan Winship <danw@gnome.org> https://bugzilla.gnome.org/show_bug.cgi?id=651756
*	Spelling correction	Yawar Amin	2012-02-04	1	-2/+2
\|
*	components: new command to list the components of a product	Dan Winship	2011-09-12	1	-0/+9
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	eg git bz components -b bugzilla.gnome.org gnome-shell or just git bz components if you have defaults configured https://bugzilla.gnome.org/show_bug.cgi?id=654693
*	Add galeon browser support	Yanko Kaneti	2011-08-28	1	-2/+2
\| \| \| \|	https://bugzilla.gnome.org/show_bug.cgi?id=632006
*	Fix 'git command --amend' typo in man page	Owen W. Taylor	2011-04-27	1	-1/+1
\| \| \| \|	Should have been 'git commit --amend'. Noticed by Matěj Cepl.
*	Add bz.add-url config variable	Owen W. Taylor	2010-09-06	1	-1/+6
\| \| \| \| \| \| \| \|	Allow specifying the default value for whether URLs are added via a new git config variable. The -u/--add-url and -n/--no-add-url override this value. Based on a patch by Xavier Claessens <xclaesse@gmail.com>
*	Document new per-tracker configuration	Owen W. Taylor	2010-09-06	1	-5/+16
\| \| \| \|	Add documentation for 'path', 'auth-user', and 'auth-password'
*	docs: Quote example url to workaround asciidoc bug	Robert Bragg	2010-06-14	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \|	The example url in the section "Ways to refer to a bug" was causing asciidoc to emit invalid xml (by closing a docbook ulink tag before the closing semicolon for a > replacement giving &gt</ulink>;) which meant that xmlto could not then produce a man page. Quoting the url seems to workaround this issue. asciidoc version was 8.4.4 https://bugzilla.gnome.org/show_bug.cgi?id=621580
*	Fix typos in documentation	Christophe Fergeau	2010-06-05	1	-9/+10
\|
*	Add 'git bz push -fix' and 'git bz edit --fix'	Owen W. Taylor	2009-09-05	1	-5/+15
\| \| \| \| \| \|	Add one-stop-shopping --fix=<bug reference> options to 'git bz push' and 'git bz edit'. These combine attaching the patches and resolving the bug for cases where review and testing aren't necessary.
*	Split out documentation	Owen W. Taylor	2009-09-05	1	-0/+358
	Move the documentation from a giant comment at the start of the file into a separate asciidoc document. Among other revisions an 'EXAMPLE SESSION' section is added to give a sense of the normal workflow. Add a Makefile and asciidoc.conf for converting the asciidoc into HTML or a man page.