Junio C Hamano writes:
> 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?
Just like for every other remote ref. If you need to know the
ultimative truth the only way is to ask the remote. Your lo
On 26 Jun 2014, at 23:04 , Junio C Hamano wrote:
> Andreas Schwab writes:
>
>> 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
Andreas Schwab writes:
> Shawn Pearce writes:
>
>> On Thu, Jun 26, 2014 at 5:42 AM, Kirill Likhodedov
>> 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
>>>
Shawn Pearce writes:
> On Thu, Jun 26, 2014 at 5:42 AM, Kirill Likhodedov
> 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
>> ..’)
>>
>> I know it is possible t
On Thu, Jun 26, 2014 at 5:42 AM, Kirill Likhodedov
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
> ..’)
>
> I know it is possible to execute 'git ls-remote’ or 'git
Hi,
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 ..’)
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 t
6 matches
Mail list logo
