All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Seymour <jon.seymour@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Dereference tag repeatedly until we get a non-tag.
Date: Tue, 12 Jul 2005 01:14:53 +1000	[thread overview]
Message-ID: <2cfc40320507110814256bef25@mail.gmail.com> (raw)
In-Reply-To: <7v8y0dx24j.fsf@assigned-by-dhcp.cox.net>

This seems reasonable to me. I have thought this would be useful on
several occasions and haven't yet conceived of a counterexample where
it would break something.

On 7/11/05, Junio C Hamano <junkio@cox.net> wrote:
> When we allow a tag object in place of a commit object, we only
> dereferenced the given tag once, which causes a tag that points
> at a tag that points at a commit to be rejected.  Instead,
> dereference tag repeatedly until we get a non-tag.
> 
> This patch makes change to two functions:
> 
>  - commit.c::lookup_commit_reference() is used by merge-base,
>    rev-tree and rev-parse to convert user supplied SHA1 to that of
>    a commit.
>  - rev-list uses its own get_commit_reference() to do the same.
> 
> Dereferencing tags this way helps both of these uses.
> 
> Signed-off-by: Junio C Hamano <junkio@cox.net>
> ---
> 
> *** Whether having a tag pointing at another tag is a separate
> *** issue, but I do not see a reason to forbid it.  Maybe it
> *** is used to represent a chain of trust.
> 
>  commit.c   |    5 +++--
>  rev-list.c |    4 ++--
>  2 files changed, 5 insertions(+), 4 deletions(-)
> 
> 0dc9377363ee73c5e3f3711d6f82e49886ce8c6a
> diff --git a/commit.c b/commit.c
> --- a/commit.c
> +++ b/commit.c
> @@ -52,8 +52,9 @@ struct commit *lookup_commit_reference(c
> 
>         if (!obj)
>                 return NULL;
> -       if (obj->type == tag_type)
> -               obj = ((struct tag *)obj)->tagged;
> +       while (obj->type == tag_type)
> +               obj = parse_object(((struct tag *)obj)->tagged->sha1);
> +
>         return check_commit(obj, sha1);
>  }
> 
> diff --git a/rev-list.c b/rev-list.c
> --- a/rev-list.c
> +++ b/rev-list.c
> @@ -367,12 +367,12 @@ static struct commit *get_commit_referen
>         /*
>          * Tag object? Look what it points to..
>          */
> -       if (object->type == tag_type) {
> +       while (object->type == tag_type) {
>                 struct tag *tag = (struct tag *) object;
>                 object->flags |= flags;
>                 if (tag_objects && !(object->flags & UNINTERESTING))
>                         add_pending_object(object, tag->tag);
> -               object = tag->tagged;
> +               object = parse_object(tag->tagged->sha1);
>         }
> 
>         /*
> 
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 


-- 
homepage: http://www.zeta.org.au/~jon/
blog: http://orwelliantremors.blogspot.com/

      reply	other threads:[~2005-07-11 18:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-09 10:00 tag referring to a commit but not directly? Junio C Hamano
2005-07-11  6:55 ` [PATCH] Dereference tag repeatedly until we get a non-tag Junio C Hamano
2005-07-11 15:14   ` Jon Seymour [this message]

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=2cfc40320507110814256bef25@mail.gmail.com \
    --to=jon.seymour@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jon@blackcubes.dyndns.org \
    --cc=junkio@cox.net \
    /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.