<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/Documentation/git-push.txt, branch v2.13.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.13.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.13.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2017-04-20T01:53:06Z</updated>
<entry>
<title>push: document &amp; test --force-with-lease with multiple remotes</title>
<updated>2017-04-20T01:53:06Z</updated>
<author>
<name>Ævar Arnfjörð Bjarmason</name>
<email>avarab@gmail.com</email>
</author>
<published>2017-04-19T09:22:03Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f17d642d3b0fa64879d59b311e596949f2a1f6d2'/>
<id>urn:sha1:f17d642d3b0fa64879d59b311e596949f2a1f6d2</id>
<content type='text'>
Document &amp; test for cases where there are two remotes pointing to the
same URL, and a background fetch &amp; subsequent `git push
--force-with-lease` shouldn't clobber un-updated references we haven't
fetched.

Some editors like Microsoft's VSC have a feature to auto-fetch in the
background, this bypasses the protections offered by
--force-with-lease &amp; --force-with-lease=&lt;refname&gt;, as noted in the
documentation being added here.

See the 'Tools that do an automatic fetch defeat "git push
--force-with-lease"' (&lt;1491617750.2149.10.camel@mattmccutchen.net&gt;)
git mailing list thread for more details. Jakub Narębski suggested
this method of adding another remote to bypass this edge case,
document that &amp; add a test for it.

Signed-off-by: Ævar Arnfjörð Bjarmason &lt;avarab@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'bw/push-submodule-only'</title>
<updated>2017-02-10T20:52:23Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2017-02-10T20:52:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8e7c1f3240d16d93f4f48c5c1ffa1d5a1f69b298'/>
<id>urn:sha1:8e7c1f3240d16d93f4f48c5c1ffa1d5a1f69b298</id>
<content type='text'>
Add missing documentation update to a recent topic.

* bw/push-submodule-only:
  completion: add completion for --recurse-submodules=only
  doc: add doc for git-push --recurse-submodules=only
</content>
</entry>
<entry>
<title>doc: add doc for git-push --recurse-submodules=only</title>
<updated>2017-02-01T23:16:49Z</updated>
<author>
<name>Cornelius Weig</name>
<email>cornelius.weig@tngtech.com</email>
</author>
<published>2017-02-01T23:07:52Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=9c24c8741e275e2fa30aa7e800c1d4610a6fe2fd'/>
<id>urn:sha1:9c24c8741e275e2fa30aa7e800c1d4610a6fe2fd</id>
<content type='text'>
Add documentation for the `--recurse-submodules=only` option of
git-push. The feature was added in commit 225e8bf (add option to
push only submodules).

Signed-off-by: Cornelius Weig &lt;cornelius.weig@tngtech.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'mm/push-social-engineering-attack-doc'</title>
<updated>2017-01-10T23:24:24Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2017-01-10T23:24:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=5f52e70879d70b211de5d6132ed96cecaa8eaf89'/>
<id>urn:sha1:5f52e70879d70b211de5d6132ed96cecaa8eaf89</id>
<content type='text'>
Doc update on fetching and pushing.

* mm/push-social-engineering-attack-doc:
  doc: mention transfer data leaks in more places
</content>
</entry>
<entry>
<title>doc: mention transfer data leaks in more places</title>
<updated>2016-11-14T19:23:07Z</updated>
<author>
<name>Matt McCutchen</name>
<email>matt@mattmccutchen.net</email>
</author>
<published>2016-11-14T18:20:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=235ec24352e151bed37063a004b9800ee0debd74'/>
<id>urn:sha1:235ec24352e151bed37063a004b9800ee0debd74</id>
<content type='text'>
The "SECURITY" section of the gitnamespaces(7) man page described two
ways for a client to steal data from a server that wasn't intended to be
shared. Similar attacks can be performed by a server on a client, so
adapt the section to cover both directions and add it to the
git-fetch(1), git-pull(1), and git-push(1) man pages. Also add
references to this section from the documentation of server
configuration options that attempt to control data leakage but may not
be fully effective.

Signed-off-by: Matt McCutchen &lt;matt@mattmccutchen.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'jk/push-force-with-lease-creation'</title>
<updated>2016-08-10T19:33:18Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-08-10T19:33:18Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e6747627865347a534e7106bb1d14e32867b234d'/>
<id>urn:sha1:e6747627865347a534e7106bb1d14e32867b234d</id>
<content type='text'>
"git push --force-with-lease" already had enough logic to allow
ensuring that such a push results in creation of a ref (i.e. the
receiving end did not have another push from sideways that would be
discarded by our force-pushing), but didn't expose this possibility
to the users.  It does so now.

* jk/push-force-with-lease-creation:
  t5533: make it pass on case-sensitive filesystems
  push: allow pushing new branches with --force-with-lease
  push: add shorthand for --force-with-lease branch creation
  Documentation/git-push: fix placeholder formatting
</content>
</entry>
<entry>
<title>Merge branch 'sb/push-options'</title>
<updated>2016-08-03T22:10:24Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2016-08-03T22:10:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=cf27c7996e986395a05c0056684923195295fd14'/>
<id>urn:sha1:cf27c7996e986395a05c0056684923195295fd14</id>
<content type='text'>
"git push" learned to accept and pass extra options to the
receiving end so that hooks can read and react to them.

* sb/push-options:
  add a test for push options
  push: accept push options
  receive-pack: implement advertising and receiving push options
  push options: {pre,post}-receive hook learns about push options
</content>
</entry>
<entry>
<title>push: add shorthand for --force-with-lease branch creation</title>
<updated>2016-07-26T20:48:09Z</updated>
<author>
<name>John Keeping</name>
<email>john@keeping.me.uk</email>
</author>
<published>2016-07-26T20:44:44Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=eee98e74f928a49c310038c77026ebc04e6cf4b2'/>
<id>urn:sha1:eee98e74f928a49c310038c77026ebc04e6cf4b2</id>
<content type='text'>
Allow the empty string to stand in for the null SHA-1 when pushing a new
branch, like we do when deleting branches.

This means that the following command ensures that `new-branch` is
created on the remote (that is, is must not already exist):

	git push --force-with-lease=new-branch: origin new-branch

Signed-off-by: John Keeping &lt;john@keeping.me.uk&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Documentation/git-push: fix placeholder formatting</title>
<updated>2016-07-25T22:21:32Z</updated>
<author>
<name>John Keeping</name>
<email>john@keeping.me.uk</email>
</author>
<published>2016-07-25T21:59:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d132b32b4e3146e4aa5a719418f85d6db1134140'/>
<id>urn:sha1:d132b32b4e3146e4aa5a719418f85d6db1134140</id>
<content type='text'>
Format the placeholder as monospace to match other occurrences in this
file and obey CodingGuidelines.

Signed-off-by: John Keeping &lt;john@keeping.me.uk&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>push: accept push options</title>
<updated>2016-07-14T22:50:41Z</updated>
<author>
<name>Stefan Beller</name>
<email>sbeller@google.com</email>
</author>
<published>2016-07-14T21:49:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=f6a4e61fbb647928d615a0befaec163a5d2bf4af'/>
<id>urn:sha1:f6a4e61fbb647928d615a0befaec163a5d2bf4af</id>
<content type='text'>
This implements everything that is required on the client side to make use
of push options from the porcelain push command.

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