[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
CG 8.2.2 - Regular maintenance, verifying issues
From: |
Federico Bruni |
Subject: |
CG 8.2.2 - Regular maintenance, verifying issues |
Date: |
Tue, 10 Nov 2015 17:31:06 +0100 |
Hi
I think that this page should be updated (there are links to google
code tracker):
http://lilypond.org/doc/v2.19/Documentation/contributor/bug-squad-checklists
The most important part is the way an issue is verified.
Let's take this issue:
https://sourceforge.net/p/testlilyissues/issues/4639/
The committish is:
0f3099177a2a23347b0a8c0895adbebc87d416be
The doc recommends two ways to verify it:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git
http://philholmes.net/lilypond/git
but, for some reason, both fail in searching that committish.
Same for gitk on my local copy.
But 'git show' works fine:
git show 0f3099177a2a23347b0a8c0895adbebc87d416be
Do you know why?
AFAIK, git log does not show if a commit was entered before a certain
tag.
There's any better way to check it?
I found this command, but you must scroll and find the committish:
git log --decorate --all --oneline --graph
Ok, I found what I think it's the best command:
git tag --contains <committish>
$ git tag --contains 0f3099177a2a23347b0a8c0895adbebc87d416be
release/2.19.31-1
What do you think?
- CG 8.2.2 - Regular maintenance, verifying issues,
Federico Bruni <=