<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/git-rebase.sh, branch v2.15.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.15.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.15.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2017-12-06T17:09:04Z</updated>
<entry>
<title>Merge branch 'tz/redirect-fix' into maint</title>
<updated>2017-12-06T17:09:04Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2017-12-06T17:09:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ce7320901f275caa1086df6fe0bfc74a7ec2fcd5'/>
<id>urn:sha1:ce7320901f275caa1086df6fe0bfc74a7ec2fcd5</id>
<content type='text'>
A few scripts (both in production and tests) incorrectly redirected
their error output.  These have been corrected.

* tz/redirect-fix:
  rebase: fix stderr redirect in apply_autostash()
  t/lib-gpg: fix gpgconf stderr redirect to /dev/null
</content>
</entry>
<entry>
<title>rebase: fix stderr redirect in apply_autostash()</title>
<updated>2017-11-14T02:51:42Z</updated>
<author>
<name>Todd Zullinger</name>
<email>tmz@pobox.com</email>
</author>
<published>2017-11-13T21:20:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=eadf1c8f454aff0b77202815af7b250320a5f5bf'/>
<id>urn:sha1:eadf1c8f454aff0b77202815af7b250320a5f5bf</id>
<content type='text'>
The intention is to ignore all output from the 'git stash apply' call.
Adjust the order of the redirection to ensure that both stdout and
stderr are redirected to /dev/null.

Signed-off-by: Todd Zullinger &lt;tmz@pobox.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'bc/rev-parse-parseopt-fix'</title>
<updated>2017-10-03T06:42:47Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2017-10-03T06:42:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b2a2c4d8099c69ec997e51cac489c0947ad17956'/>
<id>urn:sha1:b2a2c4d8099c69ec997e51cac489c0947ad17956</id>
<content type='text'>
Recent versions of "git rev-parse --parseopt" did not parse the
option specification that does not have the optional flags (*=?!)
correctly, which has been corrected.

* bc/rev-parse-parseopt-fix:
  parse-options: only insert newline in help text if needed
  parse-options: write blank line to correct output stream
  t0040,t1502: Demonstrate parse_options bugs
  git-rebase: don't ignore unexpected command line arguments
  rev-parse parseopt: interpret any whitespace as start of help text
  rev-parse parseopt: do not search help text for flag chars
  t1502: demonstrate rev-parse --parseopt option mis-parsing
</content>
</entry>
<entry>
<title>git-rebase: don't ignore unexpected command line arguments</title>
<updated>2017-09-19T03:13:09Z</updated>
<author>
<name>Brandon Casey</name>
<email>drafnel@gmail.com</email>
</author>
<published>2017-09-17T22:28:17Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=697bc8858114ddda705be6f6eb3f997b64efa659'/>
<id>urn:sha1:697bc8858114ddda705be6f6eb3f997b64efa659</id>
<content type='text'>
Currently, git-rebase will silently ignore any unexpected command-line
switches and arguments (the command-line produced by git rev-parse).
This allowed the rev-parse bug, fixed in the preceding commits, to go
unnoticed.  Let's make sure that doesn't happen again.  We shouldn't be
ignoring unexpected arguments.  Let's not.

Signed-off-by: Brandon Casey &lt;drafnel@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'kw/rebase-progress'</title>
<updated>2017-08-23T21:13:07Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2017-08-23T21:13:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=ad7d3c3b391b73207fbb29da99d4f64ad0c54f00'/>
<id>urn:sha1:ad7d3c3b391b73207fbb29da99d4f64ad0c54f00</id>
<content type='text'>
"git rebase", especially when it is run by mistake and ends up
trying to replay many changes, spent long time in silence.  The
command has been taught to show progress report when it spends
long time preparing these many changes to replay (which would give
the user a chance to abort with ^C).

* kw/rebase-progress:
  rebase: turn on progress option by default for format-patch
  format-patch: have progress option while generating patches
</content>
</entry>
<entry>
<title>rebase: turn on progress option by default for format-patch</title>
<updated>2017-08-14T21:09:46Z</updated>
<author>
<name>Kevin Willford</name>
<email>kewillf@microsoft.com</email>
</author>
<published>2017-08-10T18:32:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=9eaa858eb90802b9b6ce8a061229faba463f4bc3'/>
<id>urn:sha1:9eaa858eb90802b9b6ce8a061229faba463f4bc3</id>
<content type='text'>
Pass the "--progress" option to format-patch when the standard error
stream is connected to the terminal and "--quiet" is not given.

Signed-off-by: Kevin Willford &lt;kewillf@microsoft.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>rebase: make resolve message clearer for inexperienced users</title>
<updated>2017-07-17T21:58:19Z</updated>
<author>
<name>William Duclot</name>
<email>william.duclot@gmail.com</email>
</author>
<published>2017-07-16T19:42:20Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5fdacc17c7eb2a7b435d62d99b41f75f44f74de1'/>
<id>urn:sha1:5fdacc17c7eb2a7b435d62d99b41f75f44f74de1</id>
<content type='text'>
The git UI can be improved by addressing the error messages to those
they help: inexperienced and casual git users. To this intent, it is
helpful to make sure the terms used in those messages can be understood
by this segment of users, and that they guide them to resolve the
problem.

In particular, failure to apply a patch during a git rebase is a common
problem that can be very destabilizing for the inexperienced user. It is
important to lead them toward the resolution of the conflict (which is a
3-steps process, thus complex) and reassure them that they can escape a
situation they can't handle with "--abort". This commit answer those two
points by detailling the resolution process and by avoiding cryptic git
linguo.

Signed-off-by: William Duclot &lt;william.duclot@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'pw/rebase-i-regression-fix-tests'</title>
<updated>2017-06-30T20:45:21Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2017-06-30T20:45:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=545222471004cc3fd53c54ff53d40a8bbc3dabe6'/>
<id>urn:sha1:545222471004cc3fd53c54ff53d40a8bbc3dabe6</id>
<content type='text'>
Fix a recent regression to "git rebase -i" and add tests that would
have caught it and others.

* pw/rebase-i-regression-fix-tests:
  t3420: fix under GETTEXT_POISON build
  rebase: add more regression tests for console output
  rebase: add regression tests for console output
  rebase -i: add test for reflog message
  sequencer: print autostash messages to stderr
</content>
</entry>
<entry>
<title>sequencer: print autostash messages to stderr</title>
<updated>2017-06-19T18:09:09Z</updated>
<author>
<name>Johannes Schindelin</name>
<email>johannes.schindelin@gmx.de</email>
</author>
<published>2017-06-19T17:56:02Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=cdb866b30bd862527de597ae9c7fe7540de55bf2'/>
<id>urn:sha1:cdb866b30bd862527de597ae9c7fe7540de55bf2</id>
<content type='text'>
The rebase messages are printed to stderr traditionally. However due
to a bug introduced in 587947750bd (rebase: implement --[no-]autostash
and rebase.autostash, 2013-05-12) which was faithfully copied when
reimplementing parts of the interactive rebase in the sequencer the
autostash messages are printed to stdout instead.

It is time to fix that: let's print the autostash messages to stderr
instead of stdout.

Signed-off-by: Johannes Schindelin &lt;johannes.schindelin@gmx.de&gt;
Signed-off-by: Phillip Wood &lt;phillip.wood@dunelm.org.uk&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'gb/rebase-signoff'</title>
<updated>2017-04-26T06:39:02Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2017-04-26T06:39:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=768c7cb710a970a522320f712f028f17eabc66ed'/>
<id>urn:sha1:768c7cb710a970a522320f712f028f17eabc66ed</id>
<content type='text'>
"git rebase" learns "--signoff" option.

* gb/rebase-signoff:
  rebase: pass --[no-]signoff option to git am
  builtin/am: fold am_signoff() into am_append_signoff()
  builtin/am: honor --signoff also when --rebasing
</content>
</entry>
</feed>
