All of lore.kernel.org
 help / color / mirror / Atom feed
From: Torstein Hegge <hegge@resisty.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2013, #01; Fri, 1)
Date: Sun, 3 Nov 2013 20:15:33 +0100	[thread overview]
Message-ID: <20131103191533.GC7462@pvv.ntnu.no> (raw)
In-Reply-To: <xmqqob6320rt.fsf@gitster.dls.corp.google.com>

On Fri, Nov 01, 2013 at 15:52:06 -0700, Junio C Hamano wrote:
> * th/reflog-annotated-tag (2013-10-28) 1 commit
>   (merged to 'next' on 2013-11-01 at 8b154cc)
>  + reflog: handle lightweight and annotated tags equally
> 
>  "git log -g $annotated_tag", when there is no reflog history, should
>  have produced a single output entry (i.e. the ref creation event),
>  but instead showed the history leading to the tag.

This isn't really what th/reflog-annotated-tag does, 
"git log -g $annotated_tag" now produces no output.

Is the proper behavior to output the ref creation event? In that case,
should the same happen for lightweight tags?

Or am I missing something related to "when there is no reflog history"?


Torstein

  parent reply	other threads:[~2013-11-03 19:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 22:52 What's cooking in git.git (Nov 2013, #01; Fri, 1) Junio C Hamano
2013-11-01 23:09 ` Thomas Rast
2013-11-04 21:50   ` Junio C Hamano
2013-11-13 16:03   ` Michael Haggerty
2013-11-01 23:12 ` Ramsay Jones
2013-11-04 17:37   ` Junio C Hamano
2013-11-11 22:25     ` Junio C Hamano
2013-11-03 19:15 ` Torstein Hegge [this message]
2013-11-04 18:07   ` Junio C Hamano

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=20131103191533.GC7462@pvv.ntnu.no \
    --to=hegge@resisty.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.