summaryrefslogtreecommitdiffstats
path: root/git-bz.txt
Commit message (Collapse)AuthorAgeFilesLines
* Allow "multiplicable" attachment flagsOwen W. Taylor2015-02-271-6/+9
| | | | | | A multiplicable flag can be requested of several users. https://bugzilla.gnome.org/show_bug.cgi?id=602406
* Support for editing attachment flags.Philippe Normand2015-02-271-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | One has to first define the available flags for the bugtracker used. The only way I found is to look at the source of the bugtracker "Create New Attachment" page. Examples of use of a review: flag below. Self-review would be: review: + Requesting a review from a specific person would look like: review: ? joe@example.com To request review from a specific person as shown above, the requesteeable git-bz option of the flag has to be set to true like: git config bz-tracker.bugzilla.mozilla.org.attachment-flag.review.requesteeable true (Patch includes fixes by Owen Taylor <otaylor@redhat.com>) https://bugzilla.gnome.org/show_bug.cgi?id=602406
* Document bug references in commit messagesOwen W. Taylor2015-02-241-2/+23
| | | | | | | Add documentaton of recognized forms of bug references in commit messages, and explain the way that "See" suppresses bug reference identification. https://bugzilla.gnome.org/show_bug.cgi?id=708158
* Clarify usage of git-bz edit --fixOwen W. Taylor2015-02-241-0/+1
| | | | | Existing docs made it a bit hard to figure out how --fix works - list the usage explicitly.
* Add a ‘REPORTING BUGS’ section to the man pagePhilip Withnall2015-02-121-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 pagePhilip Withnall2015-02-121-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 subjectJasper St. Pierre2012-03-131-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 diffsDan Winship2012-03-011-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/--abortDan Winship2012-03-011-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 optionDan Winship2012-03-011-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 problemsOwen W. Taylor2012-03-011-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. Taylor2012-02-051-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 correctionYawar Amin2012-02-041-2/+2
|
* components: new command to list the components of a productDan Winship2011-09-121-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 supportYanko Kaneti2011-08-281-2/+2
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=632006
* Fix 'git command --amend' typo in man pageOwen W. Taylor2011-04-271-1/+1
| | | | Should have been 'git commit --amend'. Noticed by Matěj Cepl.
* Add bz.add-url config variableOwen W. Taylor2010-09-061-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 configurationOwen W. Taylor2010-09-061-5/+16
| | | | Add documentation for 'path', 'auth-user', and 'auth-password'
* docs: Quote example url to workaround asciidoc bugRobert Bragg2010-06-141-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 &gt; 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 documentationChristophe Fergeau2010-06-051-9/+10
|
* Add 'git bz push -fix' and 'git bz edit --fix'Owen W. Taylor2009-09-051-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 documentationOwen W. Taylor2009-09-051-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.
generated by cgit (git 2.34.1) at 2024-09-19 01:52:17 +0000