<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/builtin/push.c, branch v2.7.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.7.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.7.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2015-12-22T22:40:47Z</updated>
<entry>
<title>push: don't mark options of recurse-submodules for translation</title>
<updated>2015-12-22T22:40:47Z</updated>
<author>
<name>Ralf Thielow</name>
<email>ralf.thielow@gmail.com</email>
</author>
<published>2015-12-22T17:53:00Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6a4f2eced4036b7330742af91e8ea71e3c8b9803'/>
<id>urn:sha1:6a4f2eced4036b7330742af91e8ea71e3c8b9803</id>
<content type='text'>
Signed-off-by: Ralf Thielow &lt;ralf.thielow@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>push: follow the "last one wins" convention for --recurse-submodules</title>
<updated>2015-12-04T21:04:04Z</updated>
<author>
<name>Mike Crowe</name>
<email>mac@mcrowe.com</email>
</author>
<published>2015-12-03T13:10:35Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d34141cd08fb1c6938eae329a7c3122b05e9eb01'/>
<id>urn:sha1:d34141cd08fb1c6938eae329a7c3122b05e9eb01</id>
<content type='text'>
Use the "last one wins" convention for --recurse-submodules rather
than treating conflicting options as an error.

Also, fix the declaration of the file-scope recurse_submodules
global variable to put it on a separate line.

Signed-off-by: Mike Crowe &lt;mac@mcrowe.com&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>push: add a config option push.gpgSign for default signed pushes</title>
<updated>2015-08-19T19:58:58Z</updated>
<author>
<name>Dave Borowitz</name>
<email>dborowitz@google.com</email>
</author>
<published>2015-08-19T15:26:47Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=68c757f2199911005918aba45aa8ae0fecc72074'/>
<id>urn:sha1:68c757f2199911005918aba45aa8ae0fecc72074</id>
<content type='text'>
Signed-off-by: Dave Borowitz &lt;dborowitz@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>push: support signing pushes iff the server supports it</title>
<updated>2015-08-19T19:58:45Z</updated>
<author>
<name>Dave Borowitz</name>
<email>dborowitz@google.com</email>
</author>
<published>2015-08-19T15:26:46Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=30261094b1f7fdcba3b7a1f396e43891cd998149'/>
<id>urn:sha1:30261094b1f7fdcba3b7a1f396e43891cd998149</id>
<content type='text'>
Add a new flag --sign=true (or --sign=false), which means the same
thing as the original --signed (or --no-signed).  Give it a third
value --sign=if-asked to tell push and send-pack to send a push
certificate if and only if the server advertised a push cert nonce.

If not, warn the user that their push may not be as secure as they
thought.

Signed-off-by: Dave Borowitz &lt;dborowitz@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>push: allow --follow-tags to be set by config push.followTags</title>
<updated>2015-03-14T22:08:35Z</updated>
<author>
<name>Dave Olszewski</name>
<email>cxreg@pobox.com</email>
</author>
<published>2015-02-16T06:16:19Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a8bc269f11b34e60f5fdbd8e831a654dd6b6b67e'/>
<id>urn:sha1:a8bc269f11b34e60f5fdbd8e831a654dd6b6b67e</id>
<content type='text'>
Signed-off-by: Dave Olszewski &lt;cxreg@pobox.com&gt;
Helped-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>cmd_push: pass "flags" pointer to config callback</title>
<updated>2015-02-17T18:49:29Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2015-02-16T06:13:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=06c21e18abc9ae4647c79449a9b0a1554553ad03'/>
<id>urn:sha1:06c21e18abc9ae4647c79449a9b0a1554553ad03</id>
<content type='text'>
This will let us manipulate any transport flags which have matching
config options (there are none yet, but we will add one in
the next patch).

We could also just make "flags" a static file-scope global,
but the result is a little confusing. We end up passing it
along through do_push and push_with_options, each of which
further munge it. Having slightly-differing versions of the
flags variable available to those functions would probably
cause more confusion than it is worth. Let's just keep the
original local to cmd_push, and it can continue to pass it
through the call-stack.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>cmd_push: set "atomic" bit directly</title>
<updated>2015-02-17T18:49:18Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2015-02-16T06:12:04Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=d16c33b4c11cda583ca2b6f7b81da3ac2fdebfa4'/>
<id>urn:sha1:d16c33b4c11cda583ca2b6f7b81da3ac2fdebfa4</id>
<content type='text'>
This makes the code shorter and more obvious by removing an
unnecessary interim variable.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>git_push_config: drop cargo-culted wt_status pointer</title>
<updated>2015-02-16T06:55:11Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2015-02-16T05:46:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=06038cd7b7646333f15de663b7564cf390dcefbe'/>
<id>urn:sha1:06038cd7b7646333f15de663b7564cf390dcefbe</id>
<content type='text'>
The push config callback does not expect any incoming data
via the void pointer. And if it did, it would certainly not
be a "struct wt_status". This probably got picked up
accidentally in b945901 (push: heed user.signingkey for
signed pushes, 2014-10-22), which copied the template for
the config callback from builtin/commit.c.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'sb/atomic-push'</title>
<updated>2015-02-11T21:43:51Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-02-11T21:43:50Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=39fa6112ec8492f9300765e1f71e7c8ecfafc713'/>
<id>urn:sha1:39fa6112ec8492f9300765e1f71e7c8ecfafc713</id>
<content type='text'>
"git push" has been taught a "--atomic" option that makes push to
update more than one ref an "all-or-none" affair.

* sb/atomic-push:
  Document receive.advertiseatomic
  t5543-atomic-push.sh: add basic tests for atomic pushes
  push.c: add an --atomic argument
  send-pack.c: add --atomic command line argument
  send-pack: rename ref_update_to_be_sent to check_to_send_update
  receive-pack.c: negotiate atomic push support
  receive-pack.c: add execute_commands_atomic function
  receive-pack.c: move transaction handling in a central place
  receive-pack.c: move iterating over all commands outside execute_commands
  receive-pack.c: die instead of error in case of possible future bug
  receive-pack.c: shorten the execute_commands loop over all commands
</content>
</entry>
</feed>
