git-bz, branch master git-bz Fix typo: Uncommment => uncomment 2013-02-14T14:50:45+00:00 Owen W. Taylor otaylor@fishsoup.net 2013-02-14T14:50:45+00:00 83860382728e08e804bd12e5190570d18658caf0 Pointed out by Dan Winship 
Pointed out by Dan Winship
Add support for epiphany 3.6 2012-08-07T16:24:36+00:00 Bastien Nocera hadess@hadess.net 2012-05-17T14:12:25+00:00 1b23d76725f35555f2853ea7f5349651bdade2a4 Cookie jar got migrated from ~/.gnome2/epiphany to ~/.config/epiphany https://bugzilla.gnome.org/show_bug.cgi?id=676241 
Cookie jar got migrated from ~/.gnome2/epiphany to ~/.config/epiphany

https://bugzilla.gnome.org/show_bug.cgi?id=676241
attach: Obsolete patches with the same subject 2012-03-13T16:29:10+00:00 Jasper St. Pierre jstpierre@mecheye.net 2012-03-12T20:27:35+00:00 1cef6f1875462583e57d1543f313d4b4c585149f 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 
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: fix typo 2012-03-01T20:46:09+00:00 Owen W. Taylor otaylor@fishsoup.net 2012-03-01T20:46:09+00:00 31088e0d0ef177358831363f547084c76f8e8451 """ not """" 
""" not """"
apply: Fix addition of 'need commit message' string 2012-03-01T20:35:57+00:00 Owen W. Taylor otaylor@fishsoup.net 2012-03-01T20:35:57+00:00 be420c97d3918216f49eb91f396bfc2795de5d59 Fix a double addition of the commit message, and add a comment pointing out that the exact string is checked by git.gnome.org. 
Fix a double addition of the commit message, and add a comment
pointing out that the exact string is checked by git.gnome.org.
apply: ask the user to double-check author and subject 2012-03-01T20:31:33+00:00 Owen W. Taylor otaylor@fishsoup.net 2012-03-01T20:31:33+00:00 e1ad70be73ebf563735dd854075169bd10a9360b The author and subject might be wrong (especially the subject), when we make up a commit message for a plain patch, so ask the user to double check. 
The author and subject might be wrong (especially the subject), when
we make up a commit message for a plain patch, so ask the user to
double check.
apply: pass _interactive=True when running 'git commit --amend' 2012-03-01T20:30:04+00:00 Owen W. Taylor otaylor@fishsoup.net 2012-03-01T20:30:04+00:00 9f46b5b3b6d80fa76b33849c1b70eca9195d9145 If the editor uses the terminal, the missing _interactive=True will cause things to hang. 
If the editor uses the terminal, the missing _interactive=True will
cause things to hang.
apply: attempt to handle plain diffs 2012-03-01T18:52:04+00:00 Dan Winship danw@gnome.org 2011-08-02T14:57:48+00:00 f69a952c5d66fcd2da40d125374608c04f39960b 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 
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 2012-03-01T18:25:53+00:00 Dan Winship danw@gnome.org 2011-07-09T14:56:30+00:00 ce11237046a1af9728f7d0544c6aae8eb1d5c7d3 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 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 2012-03-01T18:24:46+00:00 Dan Winship danw@gnome.org 2011-07-09T18:10:50+00:00 e422eea9999a02262d3bad996879378ce1824541 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 
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