summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* apply: attempt to handle plain diffsDan Winship2012-03-012-2/+34
| | | | | | | | | 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-012-45/+128
| | | | | | | | | | | 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-012-10/+58
| | | | | | | | | | | | | 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
* apply: pass "-3" to git-amDan Winship2012-03-011-1/+1
| | | | | | | | | | Using 3-way merge makes it much more likely that the patch will apply correctly when the local tree is newer than the tree that the patch was generated from, and if the patch doesn't apply cleanly, git will leave a file with conflict markers rather than forcing you to reapply the patch manually. 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
* Fix up documentation generation rulesOwen W. Taylor2012-03-011-0/+4
|
* Don't strip leading space from the commit bodyOwen W. Taylor2012-02-101-4/+15
| | | | | | | If we strip leading space from the body, we'll unindent the first line of the body, which could break aligment. Based on a patch by Stef Walter <stefw@gnome.org>
* Fix parameter mistake from last patchOwen W. Taylor2012-02-071-2/+2
| | | | Pass all the necessary fields to merge_default_fields_from_dict().
* Make setting default-product, default-component in tracker config workOwen W. Taylor2012-02-061-14/+30
| | | | | | Allow setting the default-product in the tracker config. This is possibly useful for something like bugzilla.redhat.com where many repositories share a product of "Fedora".
* Support pretty bugzilla links like https://bugzilla.gnome.org/12345Colin Walters2012-02-061-2/+14
| | | | | | | Ideally I'd like git-bz to know when a Bugzilla instance supports these, but here at least we'll try parsing them. https://bugzilla.gnome.org/show_bug.cgi?id=657361
* Allow setting bz.default-<field name>Owen W. Taylor2012-02-052-7/+40
| | | | | | | | | | | 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
* Read bz.* git config upfrontOwen W. Taylor2012-02-051-38/+31
| | | | | | | Instead of making calls to git.config() as needed, read all of our options ahead of time into a dictionary initialized with defaults. Loosely based on a patch from Felipe Contreras <felipe.contreras@gmail.com>.
* Add defaults for bugs.gentoo.org.Michał Górny2012-02-041-0/+7
|
* Add the user to the cc: on the bugOwen W. Taylor2012-02-041-2/+4
| | | | | | | | | | | | | | All the logic to add the user to the cc: list on the bug is done in the web page for show_bug.cgi and not on the client side, so the option "Automatically add me to the CC list of bugs I change" in the user's preferences is not honored. Since that preference defaults to Always and users will very typically want to see further traffic on their patches, just always request the user to be added to the Cc. The main downside to this is that we do another round trip to the server when creating and attachment, and also potentially create more bug mail. https://bugzilla.gnome.org/show_bug.cgi?id=663800
* Fix a copy and paste error with auth-user and auth-passwordChris Cormack2012-02-041-2/+2
|
* Spelling correctionYawar Amin2012-02-041-2/+2
|
* Handle Unicode bug titles correctlyOwen W. Taylor2012-02-041-1/+1
| | | | | | | | If the data that we are writing into the template ends includes non-ASCII data, it will need to be encoded as UTF-8 before writing the template file. Fix from Luca Bruno. https://bugzilla.gnome.org/show_bug.cgi?id=657716
* Catch trying to refile an already filed bugOwen W. Taylor2011-09-121-0/+11
| | | | | | | If 'git bz file' is used with a commit message that contains a bug reference, prompt before filing again. https://bugzilla.gnome.org/show_bug.cgi?id=624461
* Make components work with older bugzillaOwen W. Taylor2011-09-121-9/+49
| | | | | | | | | | | | Use Bug.legal_values({ product_id: <id> }) to find out legal component values in a way that works on older Bugzilla like the bugzilla.gnome.org 3.4. This requires finding out the product_id first, which is fast with new bugzilla, but requires a slow fallback on older bugzillas; we cache positive hits for product IDs in our cache. https://bugzilla.gnome.org/show_bug.cgi?id=654693
* components: new command to list the components of a productDan Winship2011-09-122-1/+48
| | | | | | | | | | | | | | 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
* Properly close the template fileJasper St. Pierre2011-09-091-1/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=657723
* Add galeon browser supportYanko Kaneti2011-08-282-2/+10
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=632006
* Fix choice of editorDan Winship2011-08-281-13/+1
| | | | | | | | git prefers $VISUAL to $EDITOR. Most of the time. Fortunately we can just ask git what editor to use rather than trying to figure it out ourselves. https://bugzilla.gnome.org/show_bug.cgi?id=654396
* Support UTF-8 attachmentsColin Walters2011-04-271-3/+9
| | | | | | | | | | | | The cookies were being pulled out of Sqlite were Unicode, which caused the entire HTTP buffer to be Unicode. When concatenating non-ascii string instances (as would be returned from e.g. git), things blew up. Ensure the cookie data is UTF-8 str, and also set our content encoding explicitly to UTF-8. https://bugzilla.gnome.org/show_bug.cgi?id=633729
* 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.
* Fix python-2.7 compatibility with xmlrpclibOwen W. Taylor2010-09-221-14/+16
| | | | | | | | | | In Python 2.7 xmlrpclib was changed to use httplib.HTTP[S]Connection instead of the deprecatede httplib.HTTP[S]. This broke our xmlrpclib.Transport subclass which overrode make_connection(). For compatibility with old and new Python, switch to subclassing Transport and SafeTransport separately, with a mixin to add cookies. https://bugzilla.gnome.org/show_bug.cgi?id=628731
* Add bz.add-url config variableOwen W. Taylor2010-09-062-2/+13
| | | | | | | | 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>
* Use the actual description entered by the user, rather than unconditionally ↵Bobby Holley2010-09-061-1/+1
| | | | | | | | | using commit.subject By mistake, the code was discarding the description after parsing it out from the edit buffer. https://bugzilla.gnome.org/show_bug.cgi?id=628455
* Fix duplicate variable settingOwen W. Taylor2010-09-061-1/+0
| | | | | In git_run, interactive was initialized twice. Fix from Felipe Contreras <felipe.contreras@gmail.com>.
* Document new per-tracker configurationOwen W. Taylor2010-09-061-5/+16
| | | | Add documentation for 'path', 'auth-user', and 'auth-password'
* Fix inconsistent authuser/authpwd abbreviationsOwen W. Taylor2010-09-061-27/+27
| | | | | | Instead of using authuser and authpwd, spell out auth_user and auth_password (as was already done in some places.) This changes the config options to auth-user and auth-password.
* Handle partial URLsOwen W. Taylor2010-09-061-2/+6
| | | | | | Code to handle parsing a base-path out of the URL would get confused when given an URL without a path or an URL without a hostname. Catch those cases.
* Merge remote branch 'jjongsma/http-auth'Owen W. Taylor2010-09-061-13/+84
|\
| * Fix ' git bz attach' failure when bugzilla server has a pathJonathon Jongsma2009-09-151-2/+0
| | | | | | | | | | | | | | I had accidentally prepended the bugzilla installation path in both BugServer.send_post() and BugServer.send_request() (which is called by send_post()), so the path was getting prepended twice when trying to attach a patch.
| * Fix exception when parsing an alias as a urlJonathon Jongsma2009-09-151-22/+23
| | | | | | | | | | | | | | | | | | | | In BugHandle.parse(), we first try to parse the bug reference as a url and then fall back to interpreting it as an alias from the config file. Unfortunately, something like "gnome:123456" gets parsed as a url (with a scheme of 'gnome' and a path of '123456', and no hostname). This resulted in us passing a None hostname to tracker_get_auth_user(), which resulted in an uncaught exception. From now on, only proceed with treating the bug reference as a url if the scheme is parsed as 'http' or 'https'.
| * Add support for bugzilla installations that require http authJonathon Jongsma2009-09-111-8/+50
| | | | | | | | | | | | | | | | This patch should support http authentication credentials specified in url form (e.g. https://user:password@foo.com) or in a configuration file. The additional configure options are: - bz-tracker.<alias>.authuser - bz-tracker.<alias>.authpwd
| * Add support for bugzilla installations in non-root pathsJonathon Jongsma2009-09-111-12/+42
| | | | | | | | | | | | | | | | Currently, git-bz assumes that all bugzilla installations are at the root of the host (e.g. http://foo.com/). It is currently impossible to use git-bz with a bugzilla installation that is hosted at e.g. foo.com/bugzilla/. This patch adds that ability. A new configuration option ('bz-tracker.alias.path') allows the path to be specified for a host.
* | Use sqlite3 module if availableYaakov Selkowitz2010-07-011-1/+4
| | | | | | | | | | | | | | Since Python 2.5, pysqlite2 has been included in the Python standard library with the name sqlite3. https://bugzilla.gnome.org/show_bug.cgi?id=621715
* | 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 typo in google-chrome and chromium supportMarc-Andre Lureau2010-06-071-6/+6
| |
* | When prompting, loop, don't default on unknown inputsOwen W. Taylor2010-06-051-5/+9
| | | | | | | | | | | | | | Rather than taking empty or unknown input as a "no", just reprompt. I don't think the default value is obvious enough for people to actually figure it out and rely on it, so we might as well add extra robustness to accidental input.
* | Fix problem with stray spacesOwen W. Taylor2010-06-051-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | Python adds a space character between consecutive calls to print when the first print doesn't end in a newline. To avoid problems with this, use <file>.write() rather than print when: * We might be printing something empty * The newline after the line is added via echoed user input on the terminal Tracked down by William Jon McCann <william.jon.mccann@gmail.com>
* | Fix typos in documentationChristophe Fergeau2010-06-051-9/+10
| |
* | Added google-chrome as a possible browserOwen W. Taylor2010-06-051-6/+18
| | | | | | | | | | | | | | | | Chromium and Google Chrome have the same basic way of storing cookes, but different config paths. Add a google-chrome browser option with the correct config path for Google Chrome. Based on a patch by Eitan Isaacson <eitan@monotonous.org>
* | Add support for epiphany with the webkit backendJonathon Jongsma2010-06-051-2/+8
| | | | | | | | | | | | | | | | | | When they moved to webkit as the browser engine, epiphany changed the location of their cookies database, but the format remained the same. This patch adds support for the new location, but falls back to the old location if the new one doesn't exist. https://bugzilla.gnome.org/show_bug.cgi?id=609668
* | Handle 'see <url> <bug reference>'Owen W. Taylor2010-06-051-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The code that was supposed to handle 'See Mozilla bug http://bugzilla.mozilla.org/show_bug.cgi?...' as a cross reference was also detecting 'See https://developer.mozilla.org/en/SpiderMonkey/JSAPI_Reference/JS_MaybeGC https://bugzilla.gnome.org/show_bug.cgi?id=614725' As a cross-reference. Fix by requiring the "intervening words" not to have a : or / in them, since "See <url>" is clearly standalone and something with a : or a / in it is probably an URL. Reported by Adel Gadllah https://bugzilla.gnome.org/show_bug.cgi?id=619328
* | Pass --ignore-submodules when checking uncommitted changesOwen W. Taylor2010-06-051-2/+2
| | | | | | | | | | | | | | | | | | | | When we check for uncommitted changes prior to adding URLs to to commit messages we should ignore submodules, since they don't affect the rebase xprocess we use to add URLs. Reported by Benjamin Otte https://bugzilla.gnome.org/show_bug.cgi?id=611693
* | Handle Chromium cookie expiry properlyOwen W. Taylor2009-10-171-5/+16
| | | | | | | | | | | | | | | | Expiry times are in microseconds since the epoch (with the epoch depending on the exact version of Chromium.) We weren't handling this at all and just considering all cookies non-expired because of the seconds vs. microseconds difference.
* | Fix subcommands without --add-url optionOwen W. Taylor2009-09-181-1/+1
| | | | | | | | | | 'git bz add-url' was dying because the code was expecting all subcommands to have an --add-url option but add-url doesn't.
* | Fix adding-url to just some commitsOwen W. Taylor2009-09-181-28/+27
|/ | | | | Adding an URL to just some commits was broken in the rewrite to be more like git rebase, shuffle things around to fix that.
generated by cgit (git 2.34.1) at 2024-11-09 17:00:33 +0000