4ff17f10c4
This adds support to send-pack to negotiate and use atomic pushes iff the server supports it. Atomic pushes are activated by a new command line flag --atomic. In order to do this we also need to change the semantics for send_pack() slightly. The existing send_pack() function actually doesn't send all the refs back to the server when multiple refs are involved, for example when using --all. Several of the failure modes for pushes can already be detected locally in the send_pack client based on the information from the initial server side list of all the refs as generated by receive-pack. Any such refs that we thus know would fail to push are thus pruned from the list of refs we send to the server to update. For atomic pushes, we have to deal thus with both failures that are detected locally as well as failures that are reported back from the server. In order to do so we treat all local failures as push failures too. We introduce a new status code REF_STATUS_ATOMIC_PUSH_FAILED so we can flag all refs that we would normally have tried to push to the server but we did not due to local failures. This is to improve the error message back to the end user to flag that "these refs failed to update since the atomic push operation failed." Signed-off-by: Ronnie Sahlberg <sahlberg@google.com> Signed-off-by: Stefan Beller <sbeller@google.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
25 lines
440 B
C
25 lines
440 B
C
#ifndef SEND_PACK_H
|
|
#define SEND_PACK_H
|
|
|
|
struct send_pack_args {
|
|
const char *url;
|
|
unsigned verbose:1,
|
|
quiet:1,
|
|
porcelain:1,
|
|
progress:1,
|
|
send_mirror:1,
|
|
force_update:1,
|
|
use_thin_pack:1,
|
|
use_ofs_delta:1,
|
|
dry_run:1,
|
|
push_cert:1,
|
|
stateless_rpc:1,
|
|
atomic:1;
|
|
};
|
|
|
|
int send_pack(struct send_pack_args *args,
|
|
int fd[], struct child_process *conn,
|
|
struct ref *remote_refs, struct sha1_array *extra_have);
|
|
|
|
#endif
|