path: root/
AgeCommit message (Collapse)Author
2019-04-15remote-testgit: move it into the support directory for t5801Johannes Schindelin
The `git-remote-testgit` script is really only used in ``. It does not even contain any `@@<MAGIC>@@` placeholders that would need to be interpolated via `make git-remote-testgit`. Let's just move it to a new home, decluttering the top-level directory and clarifying that this is just a test helper, not an official Git command that we would want to ever support. Suggested by Ævar Arnfjörð Bjarmason. Signed-off-by: Johannes Schindelin <> Signed-off-by: Junio C Hamano <>
2015-01-22transport-helper: do not request symbolic refs to remote helpersMike Hommey
A typical remote helper will return a `list` of refs containing a symbolic ref HEAD, pointing to, e.g. refs/heads/master. In the case of a clone, all the refs are being requested through `fetch` or `import`, including the symbolic ref. While this works properly, in some cases of a fetch, like `git fetch url` or `git fetch origin HEAD`, or any fetch command involving a symbolic ref without also fetching the corresponding ref it points to, the fetch command fails with: fatal: bad object 0000000000000000000000000000000000000000 error: <remote> did not send all necessary objects (in the case the remote helper returned '?' values to the `list` command). This is because there is only one ref given to fetch(), and it's not further resolved to something at the end of fetch_with_import(). While this can be somehow handled in the remote helper itself, by adding a refspec for the symbolic ref, and storing an explicit ref in a private namespace, and then handling the `import` for that symbolic ref specifically, very few existing remote helpers are actually doing that. So, instead of requesting the exact list of wanted refs to remote helpers, treat symbolic refs differently and request the ref they point to instead. Then, resolve the symbolic refs values based on the pointed ref. This assumes there is no more than one level of indirection (a symbolic ref doesn't point to another symbolic ref). Signed-off-by: Mike Hommey <> Signed-off-by: Junio C Hamano <>
2014-06-06Merge branch 'ep/shell-assign-and-export-vars'Junio C Hamano
* ep/shell-assign-and-export-vars: scripts: more "export VAR=VALUE" fixes scripts: "export VAR=VALUE" construct is not portable
2014-05-23scripts: "export VAR=VALUE" construct is not portableElia Pinto
Found by Signed-off-by: Elia Pinto <> Reviewed-by: Jonathan Nieder <> Signed-off-by: Junio C Hamano <>
2013-11-12transport-helper: add 'force' to 'export' helpersFelipe Contreras
Otherwise they cannot know when to force the push or not (other than hacks). Tests-by: Richard Hansen <> Documentation-by: Richard Hansen <> Signed-off-by: Felipe Contreras <> Signed-off-by: Junio C Hamano <>
2013-09-03transport-helper: add no-private-update capabilityMatthieu Moy
Since 664059fb (transport-helper: update remote helper namespace, 2013-04-17), a 'push' operation on a remote helper updates the private ref by default. This is often a good thing, but it can also be desirable to disable this update to force the next 'pull' to re-import the pushed revisions. Allow remote-helpers to disable the automatic update by introducing a new capability. Signed-off-by: Matthieu Moy <> Signed-off-by: Junio C Hamano <>
2013-05-29Merge branch 'js/transport-helper-error-reporting-fix'Junio C Hamano
Finishing touches to fc/transport-helper-error-reporting topic. * js/transport-helper-error-reporting-fix: git-remote-testgit: build it to run under $SHELL_PATH git-remote-testgit: further remove some bashisms git-remote-testgit: avoid process substitution
2013-04-28git-remote-testgit: build it to run under $SHELL_PATHJunio C Hamano
Just like all the other shell scripts, replace the shebang line to make sure it runs under the shell the user specified. As this no longer depends on bashisms, t5801 does not have to say bash must be available somewhere on the system. Signed-off-by: Junio C Hamano <>