|
|
|
#include "builtin.h"
|
|
|
|
#include "cache.h"
|
|
|
|
#include "transport.h"
|
|
|
|
#include "ref-filter.h"
|
|
|
|
#include "remote.h"
|
|
|
|
#include "refs.h"
|
|
|
|
|
|
|
|
static const char * const ls_remote_usage[] = {
|
|
|
|
N_("git ls-remote [--heads] [--tags] [--refs] [--upload-pack=<exec>]\n"
|
|
|
|
" [-q | --quiet] [--exit-code] [--get-url]\n"
|
|
|
|
" [--symref] [<repository> [<refs>...]]"),
|
|
|
|
NULL
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Is there one among the list of patterns that match the tail part
|
|
|
|
* of the path?
|
|
|
|
*/
|
|
|
|
static int tail_match(const char **pattern, const char *path)
|
|
|
|
{
|
|
|
|
const char *p;
|
|
|
|
char *pathbuf;
|
|
|
|
|
|
|
|
if (!pattern)
|
|
|
|
return 1; /* no restriction */
|
|
|
|
|
|
|
|
pathbuf = xstrfmt("/%s", path);
|
|
|
|
while ((p = *(pattern++)) != NULL) {
|
|
|
|
if (!wildmatch(p, pathbuf, 0)) {
|
|
|
|
free(pathbuf);
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
free(pathbuf);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
int cmd_ls_remote(int argc, const char **argv, const char *prefix)
|
|
|
|
{
|
|
|
|
const char *dest = NULL;
|
Improve git-peek-remote
This makes git-peek-remote able to basically do everything that
git-ls-remote does (but obviously just for the native protocol, so no
http[s]: or rsync: support).
The default behaviour is the same, but you can now give a mixture of
"--refs", "--tags" and "--heads" flags, where "--refs" forces
git-peek-remote to only show real refs (ie none of the fakey tag lookups,
but also not the special pseudo-refs like HEAD and MERGE_HEAD).
The "--tags" and "--heads" flags respectively limit the output to just
regular tags and heads, of course.
You can still also ask to limit them by name too.
You can combine the flags, so
git peek-remote --refs --tags .
will show all local _true_ tags, without the generated tag lookups
(compare the output without the "--refs" flag).
And "--tags --heads" will show both tags and heads, but will avoid (for
example) any special refs outside of the standard locations.
I'm also planning on adding a "--ignore-local" flag that allows us to ask
it to ignore any refs that we already have in the local tree, but that's
an independent thing.
All this is obviously gearing up to making "git fetch" cheaper.
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
19 years ago
|
|
|
unsigned flags = 0;
|
|
|
|
int get_url = 0;
|
|
|
|
int quiet = 0;
|
|
|
|
int status = 0;
|
|
|
|
int show_symref_target = 0;
|
|
|
|
const char *uploadpack = NULL;
|
|
|
|
const char **pattern = NULL;
|
|
|
|
struct strvec ref_prefixes = STRVEC_INIT;
|
|
|
|
int i;
|
|
|
|
struct string_list server_options = STRING_LIST_INIT_DUP;
|
|
|
|
|
|
|
|
struct remote *remote;
|
|
|
|
struct transport *transport;
|
|
|
|
const struct ref *ref;
|
|
|
|
struct ref_array ref_array;
|
|
|
|
static struct ref_sorting *sorting = NULL, **sorting_tail = &sorting;
|
|
|
|
|
|
|
|
struct option options[] = {
|
|
|
|
OPT__QUIET(&quiet, N_("do not print remote URL")),
|
|
|
|
OPT_STRING(0, "upload-pack", &uploadpack, N_("exec"),
|
|
|
|
N_("path of git-upload-pack on the remote host")),
|
|
|
|
{ OPTION_STRING, 0, "exec", &uploadpack, N_("exec"),
|
|
|
|
N_("path of git-upload-pack on the remote host"),
|
|
|
|
PARSE_OPT_HIDDEN },
|
|
|
|
OPT_BIT('t', "tags", &flags, N_("limit to tags"), REF_TAGS),
|
|
|
|
OPT_BIT('h', "heads", &flags, N_("limit to heads"), REF_HEADS),
|
|
|
|
OPT_BIT(0, "refs", &flags, N_("do not show peeled tags"), REF_NORMAL),
|
|
|
|
OPT_BOOL(0, "get-url", &get_url,
|
|
|
|
N_("take url.<base>.insteadOf into account")),
|
parse_opt_ref_sorting: always use with NONEG flag
The "--sort" parameter of for-each-ref, etc, does not handle negation,
and instead returns an error to the parse-options code. But neither
piece of code prints anything for the user, which may leave them
confused:
$ git for-each-ref --no-sort
$ echo $?
129
As the comment in the callback function notes, this probably should
clear the list, which would make it consistent with other list-like
options (i.e., anything that uses OPT_STRING_LIST currently).
Unfortunately that's a bit tricky due to the way the ref-filter code
works. But in the meantime, let's at least make the error a little less
confusing:
- switch to using PARSE_OPT_NONEG in the option definition, which will
cause the options code to produce a useful message
- since this was cut-and-pasted to four different spots, let's define
a single OPT_REF_SORT() macro that we can use everywhere
- the callback can use BUG_ON_OPT_NEG() to make sure the correct flags
are used (incidentally, this also satisfies -Wunused-parameters,
since we're now looking at "unset")
- expand the comment into a NEEDSWORK to make it clear that the
direction is right, but the details need to be worked out
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
6 years ago
|
|
|
OPT_REF_SORT(sorting_tail),
|
|
|
|
OPT_SET_INT_F(0, "exit-code", &status,
|
|
|
|
N_("exit with exit code 2 if no matching refs are found"),
|
|
|
|
2, PARSE_OPT_NOCOMPLETE),
|
|
|
|
OPT_BOOL(0, "symref", &show_symref_target,
|
|
|
|
N_("show underlying ref in addition to the object pointed by it")),
|
|
|
|
OPT_STRING_LIST('o', "server-option", &server_options, N_("server-specific"), N_("option to transmit")),
|
|
|
|
OPT_END()
|
|
|
|
};
|
|
|
|
|
|
|
|
memset(&ref_array, 0, sizeof(ref_array));
|
|
|
|
|
|
|
|
argc = parse_options(argc, argv, prefix, options, ls_remote_usage,
|
|
|
|
PARSE_OPT_STOP_AT_NON_OPTION);
|
|
|
|
dest = argv[0];
|
|
|
|
|
|
|
|
UNLEAK(sorting);
|
|
|
|
|
|
|
|
if (argc > 1) {
|
|
|
|
int i;
|
|
|
|
pattern = xcalloc(argc, sizeof(const char *));
|
|
|
|
for (i = 1; i < argc; i++) {
|
|
|
|
pattern[i - 1] = xstrfmt("*/%s", argv[i]);
|
|
|
|
}
|
|
|
|
}
|
Improve git-peek-remote
This makes git-peek-remote able to basically do everything that
git-ls-remote does (but obviously just for the native protocol, so no
http[s]: or rsync: support).
The default behaviour is the same, but you can now give a mixture of
"--refs", "--tags" and "--heads" flags, where "--refs" forces
git-peek-remote to only show real refs (ie none of the fakey tag lookups,
but also not the special pseudo-refs like HEAD and MERGE_HEAD).
The "--tags" and "--heads" flags respectively limit the output to just
regular tags and heads, of course.
You can still also ask to limit them by name too.
You can combine the flags, so
git peek-remote --refs --tags .
will show all local _true_ tags, without the generated tag lookups
(compare the output without the "--refs" flag).
And "--tags --heads" will show both tags and heads, but will avoid (for
example) any special refs outside of the standard locations.
I'm also planning on adding a "--ignore-local" flag that allows us to ask
it to ignore any refs that we already have in the local tree, but that's
an independent thing.
All this is obviously gearing up to making "git fetch" cheaper.
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Signed-off-by: Junio C Hamano <junkio@cox.net>
19 years ago
|
|
|
|
|
|
|
if (flags & REF_TAGS)
|
|
|
|
strvec_push(&ref_prefixes, "refs/tags/");
|
|
|
|
if (flags & REF_HEADS)
|
|
|
|
strvec_push(&ref_prefixes, "refs/heads/");
|
|
|
|
|
|
|
|
remote = remote_get(dest);
|
ls-remote: fall-back to default remotes when no remote specified
Instead of breaking execution when no remote (as specified in the
variable dest) is specified when git-ls-remote is invoked, continue on
and let remote_get() handle it.
This way, we are able to use the default remotes (eg. "origin",
branch.<name>.remote), as git-fetch, git-push, and other users of
remote_get(), do.
If no suitable remote is found, exit with a message describing the
issue, instead of just the usage text, as we do previously.
Add several tests to check that git-ls-remote handles the
no-remote-specified situation.
Also add a test that "git ls-remote <pattern>" does not work; we are
unable to guess the remote in that situation, as are git-fetch and
git-push.
In that test, we are testing for messages coming from two separate
processes, but we should be OK, because the second message is triggered
by closing the fd which must happen after the first message is printed.
(analysis by Jeff King.)
Signed-off-by: Tay Ray Chuan <rctay89@gmail.com>
Acked-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
15 years ago
|
|
|
if (!remote) {
|
|
|
|
if (dest)
|
|
|
|
die("bad repository '%s'", dest);
|
|
|
|
die("No remote configured to list refs from.");
|
|
|
|
}
|
|
|
|
if (!remote->url_nr)
|
|
|
|
die("remote %s has no configured URL", dest);
|
|
|
|
|
|
|
|
if (get_url) {
|
|
|
|
printf("%s\n", *remote->url);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
transport = transport_get(remote, NULL);
|
|
|
|
if (uploadpack != NULL)
|
|
|
|
transport_set_option(transport, TRANS_OPT_UPLOADPACK, uploadpack);
|
|
|
|
if (server_options.nr)
|
|
|
|
transport->server_options = &server_options;
|
|
|
|
|
|
|
|
ref = transport_get_remote_refs(transport, &ref_prefixes);
|
builtin/ls-remote: initialize repository based on fetch
ls-remote may or may not operate within a repository, and as such will
not have been initialized with the repository's hash algorithm. Even if
it were, the remote side could be using a different algorithm and we
would still want to display those refs properly. Find the hash
algorithm used by the remote side by querying the transport object and
set our hash algorithm accordingly.
Without this change, if the remote side is using SHA-256, we truncate
the refs to 40 hex characters, since that's the length of the default
hash algorithm (SHA-1).
Note that technically this is not a correct setting of the repository
hash algorithm since, if we are in a repository, it might be one of a
different hash algorithm from the remote side. However, our current
code paths don't handle multiple algorithms and won't for some time, so
this is the best we can do. We rely on the fact that ls-remote never
modifies the current repository, which is a reasonable assumption to
make.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
5 years ago
|
|
|
if (ref) {
|
|
|
|
int hash_algo = hash_algo_by_ptr(transport_get_hash_algo(transport));
|
|
|
|
repo_set_hash_algo(the_repository, hash_algo);
|
|
|
|
}
|
|
|
|
if (transport_disconnect(transport))
|
|
|
|
return 1;
|
|
|
|
|
|
|
|
if (!dest && !quiet)
|
|
|
|
fprintf(stderr, "From %s\n", *remote->url);
|
|
|
|
for ( ; ref; ref = ref->next) {
|
|
|
|
struct ref_array_item *item;
|
|
|
|
if (!check_ref_type(ref, flags))
|
|
|
|
continue;
|
|
|
|
if (!tail_match(pattern, ref->name))
|
|
|
|
continue;
|
|
|
|
item = ref_array_push(&ref_array, ref->name, &ref->old_oid);
|
|
|
|
item->symref = xstrdup_or_null(ref->symref);
|
|
|
|
}
|
|
|
|
|
|
|
|
if (sorting)
|
|
|
|
ref_array_sort(sorting, &ref_array);
|
|
|
|
|
|
|
|
for (i = 0; i < ref_array.nr; i++) {
|
|
|
|
const struct ref_array_item *ref = ref_array.items[i];
|
|
|
|
if (show_symref_target && ref->symref)
|
|
|
|
printf("ref: %s\t%s\n", ref->symref, ref->refname);
|
|
|
|
printf("%s\t%s\n", oid_to_hex(&ref->objectname), ref->refname);
|
|
|
|
status = 0; /* we found something */
|
|
|
|
}
|
|
|
|
|
|
|
|
ref_array_clear(&ref_array);
|
|
|
|
return status;
|
|
|
|
}
|