[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [jgit-dev] Re: [egit-dev] RFC: How to display "detached" HEAD in Git Label Decorations
- From: Matthias Sohn <matthias.sohn@xxxxxxxxxxxxxx>
- Date: Mon, 10 May 2010 18:24:16 +0200
- Delivered-to: firstname.lastname@example.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=bGLoa7hdSFz5r9AYIFyqbSDSPl95Rjibi39KBn+HVJZoB0Hq7mQLNTX+H2xt4PdAA+ 05O2UJfE3h1YjPPPy35foAXsONn9WFE+/K69Q88CyYBE7pSjDcr/zU0jJMo/G8/XdIGZ H2kPF/4m3+nrgMvslKyk/UQE8m3TcCjwl/9d4=
2010/5/10 Shawn O. Pearce <spearce@xxxxxxxxxxx>
> The remaining question would be how to react in cases when there is more than one tag and/or remote branch for the same commit.If there is both a remote branch and a tag, use the tag.
If there are multiple tags, use the tag with the most recent
tagger date. If none of the tags have a tagger (these are older
style tags), sort them by name and pick the last one.
If there are no tags, but multiple remote branches, sort them by
name and pick the last one.
I don't think this case of multiple refs per commit shows up often
> Alternatively, we could always just show the shortened commit id with ellipsis and offer a specific UI to display tags/remote branches that point to that commit.
enough to do this. But, it might be useful for some users. Me,
I'd probably never use it.
The commit graph in the history view already shows this information.
I think that should be sufficient.