| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=632006
|
|
|
|
| |
Should have been 'git commit --amend'. Noticed by Matěj Cepl.
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Add documentation for 'path', 'auth-user', and 'auth-password'
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 ></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
|
| |
|
|
|
|
|
|
| |
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.
|
|
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.
|