<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/git-push.txt, branch v2.8.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.8.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.8.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2016-02-26T21:37:21Z</updated>
<entry>
<title>Merge branch 'mm/push-simple-doc'</title>
<updated>2016-02-26T21:37:21Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-02-26T21:37:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=1e4c08ff7e0f1d17b4a8e2c04edca8fc00455881'/>
<id>urn:sha1:1e4c08ff7e0f1d17b4a8e2c04edca8fc00455881</id>
<content type='text'>
The documentation did not clearly state that the 'simple' mode is
now the default for "git push" when push.default configuration is
not set.

* mm/push-simple-doc:
  Documentation/git-push: document that 'simple' is the default
</content>
</entry>
<entry>
<title>Merge branch 'ew/force-ipv4'</title>
<updated>2016-02-24T21:25:54Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-02-24T21:25:54Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e84d5e9fa178a027b1c8b9f6e22c9173dcda03b3'/>
<id>urn:sha1:e84d5e9fa178a027b1c8b9f6e22c9173dcda03b3</id>
<content type='text'>
"git fetch" and friends that make network connections can now be
told to only use ipv4 (or ipv6).

* ew/force-ipv4:
  connect &amp; http: support -4 and -6 switches for remote operations
</content>
</entry>
<entry>
<title>Documentation/git-push: document that 'simple' is the default</title>
<updated>2016-02-23T21:35:10Z</updated>
<author>
<name>Matthieu Moy</name>
<email>Matthieu.Moy@imag.fr</email>
</author>
<published>2016-02-23T21:04:41Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f6b1fb372ee164e4cb2d15a9a325e13685f9dc2d'/>
<id>urn:sha1:f6b1fb372ee164e4cb2d15a9a325e13685f9dc2d</id>
<content type='text'>
The default behavior is well documented already in git-config(1), but
git-push(1) itself did not mention it at all. For users willing to learn
how "git push" works but not how to configure it, this makes the
documentation cumbersome to read.

Make the git-push(1) page self-contained by adding a short summary of
what 'push.default=simple' does, early in the page.

Signed-off-by: Matthieu Moy &lt;Matthieu.Moy@imag.fr&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>connect &amp; http: support -4 and -6 switches for remote operations</title>
<updated>2016-02-12T19:34:14Z</updated>
<author>
<name>Eric Wong</name>
<email>normalperson@yhbt.net</email>
</author>
<published>2016-02-03T04:09:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=c915f11eb4922e154e29cf62d3b549d65c06a170'/>
<id>urn:sha1:c915f11eb4922e154e29cf62d3b549d65c06a170</id>
<content type='text'>
Sometimes it is necessary to force IPv4-only or IPv6-only operation
on networks where name lookups may return a non-routable address and
stall remote operations.

The ssh(1) command has an equivalent switches which we may pass when
we run them.  There may be old ssh(1) implementations out there
which do not support these switches; they should report the
appropriate error in that case.

rsync support is untouched for now since it is deprecated and
scheduled to be removed.

Signed-off-by: Eric Wong &lt;normalperson@yhbt.net&gt;
Reviewed-by: Torsten Bögershausen &lt;tboegi@web.de&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'ps/push-delete-option'</title>
<updated>2016-01-12T23:16:54Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-01-12T23:16:53Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7b9d1b9556b31fe5f661caa1e82856ca876f2a08'/>
<id>urn:sha1:7b9d1b9556b31fe5f661caa1e82856ca876f2a08</id>
<content type='text'>
"branch --delete" has "branch -d" but "push --delete" does not.

* ps/push-delete-option:
  push: add '-d' as shorthand for '--delete'
  push: add '--delete' flag to synopsis
</content>
</entry>
<entry>
<title>push: add '-d' as shorthand for '--delete'</title>
<updated>2015-12-16T20:30:10Z</updated>
<author>
<name>Patrick Steinhardt</name>
<email>ps@pks.im</email>
</author>
<published>2015-12-14T15:23:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=38a2559113d62b0f67ed968db9ca82330b702a9c'/>
<id>urn:sha1:38a2559113d62b0f67ed968db9ca82330b702a9c</id>
<content type='text'>
"git push" takes "--delete" but does not take a short form "-d",
unlike "git branch" which does take both.  Bring consistency
between them.

Signed-off-by: Patrick Steinhardt &lt;ps@pks.im&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>push: add '--delete' flag to synopsis</title>
<updated>2015-12-14T21:47:03Z</updated>
<author>
<name>Patrick Steinhardt</name>
<email>ps@pks.im</email>
</author>
<published>2015-12-14T15:23:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=fff69f7053b175be5963b08f802e0e03dccd696a'/>
<id>urn:sha1:fff69f7053b175be5963b08f802e0e03dccd696a</id>
<content type='text'>
The delete flag is not mentioned in the synopsis of `git-push`.
Add the flag to make it more discoverable.

Signed-off-by: Patrick Steinhardt &lt;ps@pks.im&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>push: add recurseSubmodules config option</title>
<updated>2015-11-20T13:02:07Z</updated>
<author>
<name>Mike Crowe</name>
<email>mac@mcrowe.com</email>
</author>
<published>2015-11-17T11:05:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b33a15b08131514b593015cb3e719faf9db20208'/>
<id>urn:sha1:b33a15b08131514b593015cb3e719faf9db20208</id>
<content type='text'>
The --recurse-submodules command line parameter has existed for some
time but it has no config file equivalent.

Following the style of the corresponding parameter for git fetch, let's
invent push.recurseSubmodules to provide a default for this
parameter. This also requires the addition of --recurse-submodules=no to
allow the configuration to be overridden on the command line when
required.

The most straightforward way to implement this appears to be to make
push use code in submodule-config in a similar way to fetch.

Signed-off-by: Mike Crowe &lt;mac@mcrowe.com&gt;
Signed-off-by: Jeff King &lt;peff@peff.net&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jc/em-dash-in-doc'</title>
<updated>2015-10-29T20:59:16Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-10-29T20:59:16Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=73167677c0a0e51b3b6505a4287dd3cbf7f11497'/>
<id>urn:sha1:73167677c0a0e51b3b6505a4287dd3cbf7f11497</id>
<content type='text'>
AsciiDoc markup fixes.

* jc/em-dash-in-doc:
  Documentation: AsciiDoc spells em-dash as double-dashes, not triple
</content>
</entry>
<entry>
<title>Documentation: AsciiDoc spells em-dash as double-dashes, not triple</title>
<updated>2015-10-22T20:02:33Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-10-22T20:02:33Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=3b19dba7030f179cf981a8714693f74c07d915a4'/>
<id>urn:sha1:3b19dba7030f179cf981a8714693f74c07d915a4</id>
<content type='text'>
Again, we do not usually process release notes with AsciiDoc, but it
is better to be consistent.

This incidentally reveals breakages left by an ancient 5e00439f
(Documentation: build html for all files in technical and howto,
2012-10-23).  The index-format documentation was originally written
to be read as straight text without formatting and when the commit
forced everything in Documentation/ to go through AsciiDoc, it did
not do any adjustment--hence the double-dashes will be seen in the
resulting text that is rendered as preformatted fixed-width without
converted into em-dashes.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
