Git atomic

(or when an --exec option was provided).This is the same as specifying the --reschedule-failed-exec option. rebase.forkPoint If set to false set --no-fork-point option by default. receive.advertiseAtomic By default, git-receive-pack will advertise the atomic pushcapability to its clients. If you don’t want to advertise thiscapability, set this variable to false. receive.advertisePushOptions When set to true, git-receive-pack will advertise the push optionscapability to its clients. False by default. receive.autogc By default, git-receive-pack will run "git-gc --auto" afterreceiving data from git-push and updating refs. You can stopit by setting this variable to false. receive.certNonceSeed By setting this variable to a string, git receive-packwill accept a git push --signed and verifies it by usinga "nonce" protected by HMAC using this string as a secretkey. receive.certNonceSlop When a git push --signed sent a push certificate with a"nonce" that was issued by a receive-pack serving the samerepository within this many seconds, export the "nonce"found in the certificate to GIT_PUSH_CERT_NONCE to thehooks (instead of what the receive-pack asked the sendingside to include). This may allow writing checks inpre-receive and post-receive a bit easier. Instead ofchecking GIT_PUSH_CERT_NONCE_SLOP environment variablethat records by how many seconds the nonce is stale todecide if they want to accept the certificate, they onlycan check GIT_PUSH_CERT_NONCE_STATUS is OK. receive.fsckObjects If it is set to true, git-receive-pack will check all receivedobjects. See transfer.fsckObjects for what’s checked.Defaults to false. If not set, the value oftransfer.fsckObjects is used instead. receive.fsck. Acts like fsck., but is used bygit-receive-pack[1] instead ofgit-fsck[1]. See the fsck. documentation fordetails. receive.fsck.skipList Acts like

The server’s ref advertisement to find commitsin common. rebase.backend Default backend to use for rebasing. Possible choices areapply or merge. In the future, if the merge backend gainsall remaining capabilities of the apply backend, this settingmay become unused. rebase.stat Whether to show a diffstat of what changed upstream since the lastrebase. False by default. rebase.autoSquash If set to true enable --autosquash option by default. rebase.autoStash When set to true, automatically create a temporary stash entrybefore the operation begins, and apply it after the operationends. This means that you can run rebase on a dirty worktree.However, use with care: the final stash application after asuccessful rebase might result in non-trivial conflicts.This option can be overridden by the --no-autostash and--autostash options of git-rebase[1].Defaults to false. rebase.missingCommitsCheck If set to "warn", git rebase -i will print a warning if somecommits are removed (e.g. a line was deleted), however therebase will still proceed. If set to "error", it will printthe previous warning and stop the rebase, git rebase--edit-todo can then be used to correct the error. If set to"ignore", no checking is done.To drop a commit without warning or error, use the dropcommand in the todo list.Defaults to "ignore". rebase.instructionFormat A format string, as specified in git-log[1], to be used for thetodo list during an interactive rebase. The format willautomatically have the long commit hash prepended to the format. rebase.abbreviateCommands If set to true, git rebase will use abbreviated command names in thetodo list resulting in something like this: p deadbee The oneline of the commit p fa1afe1 The oneline of the next commit ...instead of: pick deadbee The oneline of the commit pick fa1afe1 The oneline of the next commit ...Defaults to false. rebase.rescheduleFailedExec Automatically reschedule exec commands that failed. This only makessense in interactive mode (or when an --exec option was provided).This is the same as specifying the --reschedule-failed-exec option. rebase.forkPoint If set to false set --no-fork-point option by default. receive.advertiseAtomic By default, git-receive-pack will advertise the atomic pushcapability to its clients. If you don’t want to advertise thiscapability, set this variable to false. receive.advertisePushOptions When set to true, git-receive-pack will advertise

With access to your Helix Core Server. Spec depot: when enabled by your Helix Core Server administrator, a spec depot stores the history of changes to Helix Core Server specifications, such as changelistsThe changes to files or stream specifications along with metadata, such as the list of changed files, their version numbers, who submitted the changelist to the depot, and the submitter's description of the changes. A changelist is the unit of versioned work. See also atomic change transaction and changelist number.. Graph depot: A depot for storing files in a repo , which uses the graph model associated with git instead of the "classic" Perforce file revision model. Workspaces Workspace associated with a classic depot Workspace associated with a stream depot Workspace when stream spec is checked out for edit Workspace associated with a graph depot, which might or might not be a hybrid workspaceA client workspace that supports both repos of type graph (see 'Git Connector') and the classic Helix Core file revision model. Swarm Pending changelist with shelved files in Swarm review Empty pending changelist with shelved files in Swarm review Submitted changelist with Swarm review Folder History with Swarm review

...instead of: pick deadbee The oneline of the commit pick fa1afe1 The oneline of the next commit ...Defaults to false. rebase.rescheduleFailedExec Automatically reschedule exec commands that failed. This only makessense in interactive mode (or when an --exec option was provided).This is the same as specifying the --reschedule-failed-exec option. receive.advertiseAtomic By default, git-receive-pack will advertise the atomic pushcapability to its clients. If you don’t want to advertise thiscapability, set this variable to false. receive.advertisePushOptions When set to true, git-receive-pack will advertise the push optionscapability to its clients. False by default. receive.autogc By default, git-receive-pack will run "git-gc --auto" afterreceiving data from git-push and updating refs. You can stopit by setting this variable to false. receive.certNonceSeed By setting this variable to a string, git receive-packwill accept a git push --signed and verifies it by usinga "nonce" protected by HMAC using this string as a secretkey. receive.certNonceSlop When a git push --signed sent a push certificate with a"nonce" that was issued by a receive-pack serving the samerepository within this many seconds, export the "nonce"found in the certificate to GIT_PUSH_CERT_NONCE to thehooks (instead of what the receive-pack asked the sendingside to include). This may allow writing checks inpre-receive and post-receive a bit easier. Instead ofchecking GIT_PUSH_CERT_NONCE_SLOP environment variablethat records by how many seconds the nonce is stale todecide if they want to accept the certificate, they onlycan check GIT_PUSH_CERT_NONCE_STATUS is OK. receive.fsckObjects If it is set to true, git-receive-pack will check all receivedobjects. See transfer.fsckObjects for what’s checked.Defaults to false. If not set, the value oftransfer.fsckObjects is used instead. receive.fsck. Acts like fsck., but is used bygit-receive-pack[1] instead ofgit-fsck[1]. See the fsck. documentation fordetails. receive.fsck.skipList Acts like fsck.skipList, but is used bygit-receive-pack[1] instead ofgit-fsck[1]. See the fsck.skipList documentation fordetails. receive.keepAlive After receiving the pack from the client, receive-pack mayproduce no output (if --quiet was specified) while processingthe pack, causing some networks to drop the TCP connection.With this option set, if receive-pack does not transmitany data in this phase for receive.keepAlive seconds, it willsend a short keepalive packet. The default is 5 seconds; setto 0 to disable keepalives entirely. receive.unpackLimit If the number of objects received in a push is below thislimit then the objects will be unpacked into loose objectfiles. However if the number of received objects equals orexceeds this limit then the received pack will be stored asa pack, after adding any missing delta bases. Storing thepack from a push can make the push operation complete faster,especially on slow filesystems. If not set, the value oftransfer.unpackLimit is used instead. receive.maxInputSize If the size of the incoming pack stream is larger than thislimit, then git-receive-pack will error out, instead ofaccepting the pack file. If not set or set to 0, then the sizeis unlimited.