From: Junio C Hamano <gitster@pobox.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Shawn Pearce <spearce@spearce.org>,
Kirill Likhodedov <kirill.likhodedov@jetbrains.com>,
git <git@vger.kernel.org>
Subject: Re: Is it possible to list unpushed tags without accessing remote?
Date: Thu, 26 Jun 2014 12:04:29 -0700 [thread overview]
Message-ID: <xmqqlhsj4hmq.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <874mz76281.fsf@igel.home> (Andreas Schwab's message of "Thu, 26 Jun 2014 18:54:22 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
> Shawn Pearce <spearce@spearce.org> writes:
>
>> On Thu, Jun 26, 2014 at 5:42 AM, Kirill Likhodedov
>> <kirill.likhodedov@jetbrains.com> wrote:
>>> is it possible to know which tags are not yet pushed to a remote via a completely local command?
>>>
>>> (e.g. the list of unpushed _commits_ may be received by ‘git log <upstream>..’)
>>>
>>> I know it is possible to execute 'git ls-remote’ or 'git push --dry-run’, but both ask the remote server.
>>> I’m almost sure that the answer is “NO”, but want to receive a confirmation from Git gurus :)
>>
>> No. The client doesn't track what tags the remote has.
>
> Not by default, but it is easy to configure your clone to fetch tags to
> a separate namespace.
But then in order to learn what tags the remote has, you need to
talk to the remote and it won't be "complately a local" operation
anymore, no?
next prev parent reply other threads:[~2014-06-26 19:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 12:42 Is it possible to list unpushed tags without accessing remote? Kirill Likhodedov
2014-06-26 16:13 ` Shawn Pearce
2014-06-26 16:54 ` Andreas Schwab
2014-06-26 19:04 ` Junio C Hamano [this message]
2014-06-26 19:20 ` Kirill Likhodedov
2014-06-27 7:41 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqlhsj4hmq.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=kirill.likhodedov@jetbrains.com \
--cc=schwab@linux-m68k.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).