On Fri, Sep 4, 2015 at 5:19 AM, John Keeping wrote:
> I think it would be a reasonable enhancement to include the branch name
> in the reflog message if "-b" is given to "git clone", but I'm not aware
> of any (formal) policy on the format of reflog messages so relying on
>
[It looks like your reply didn't get through to the mailing list,
presumably because it contained a text/html part.]
On Fri, Sep 04, 2015 at 04:22:04AM -0600, Jesse Hopkins wrote:
> On Sep 4, 2015 1:54 AM, "John Keeping" wrote:
> > When I checkout a tag, "git reflog -1"
On Thu, Sep 03, 2015 at 08:53:16PM -0600, Jesse Hopkins wrote:
> Looking for suggestions on how to determine the tag that was used to
> checkout a git repo to its associated commit, particularly in the case
> where multiple tags might point to the same commit.
>
> I've had a look at git-name-rev
On Thu, Sep 3, 2015 at 7:53 PM, Jesse Hopkins wrote:
>
> It seems to me that when checking out to a tag, Git does not record the
> *name* of the tag anywhere, but rather sets HEAD to the de-referenced
> commit SHA-1. As far as I can tell, it is not possible to recover the
Hello all,
Looking for suggestions on how to determine the tag that was used to
checkout a git repo to its associated commit, particularly in the case
where multiple tags might point to the same commit.
I've had a look at git-name-rev and git-describe, and both seem useful so
long as there's
5 matches
Mail list logo