Pierre, Gergely, Dale
Thanks very much, somehow I missed your responses until this morning. I
have passed on your suggestions and I think satisfied the boss. for now.
On Saturday, June 14, 2014 4:30:17 AM UTC-7, Pierre-François CLEMENT wrote:
Le mercredi 11 juin 2014 18:50:07 UTC+2, John
Now that we know this, git-bisect is exactly the tool he needs! He
specifies the last known commit without the bug, and the first known commit
with the bug. Git will then choose intermediate commits for you to test if
the bug still exists, and point you to the first bad one.
Hope that helps.
On
From: Gergely Polonkai gerg...@polonkai.eu
Now that we know this, git-bisect is exactly the tool he needs! He
specifies the last known commit without the bug, and the first known commit
with the bug. Git will then choose intermediate commits for you to test if
the bug still exists, and point
git-ls-tree prints the blob’s (file’s) hash. It has nothing to do with
a commit, which has its own hash (as you have already noticed).
As far as I can get, your boss needs a commit hash, as he wants to
know who and when introduced the bug. For that, you can even use
git-bisect (as I suggested
From: John Fisher fishook2...@gmail.com
[...]
[1:text/plain Hide] *but that output does not agree with git log!*
I am totally lost what you're talking about.
git log lists *commits* and their SHAs. You say you entered git
log rmapi_bcmxlat.c and you seem to expect it to contain the SHAs
Trying to make things a bit more clean… @John Fisher, you (and maybe
your boss) might want to read [1] which somewhat explains git’s
private parts, and how exactly it works. Not the most complete list
(to be honest, I’ve seen a better one *somewhere*, I just lost the
link :( Anyways, I hope it
On Monday, June 9, 2014 12:36:57 PM UTC-7, Dale Worley wrote:
You're not clear what the question is. You ask which version of a
file is in the tag and the answer is the version with hash
990c3e0f7efc8ddf869dbb39ba0065c9e9578df4.
Do you mean Which commit introduced that version of
From: John Fisher fishook2...@gmail.com
The SHA for the tag is not the SHA for the individual file. OK thats
obvious to experienced Git users, and the main point here. He wants to know
what the SHA for the file is just prior to the tag, (shown in Gitk BTW) . I
have shown him how to get
On Tuesday, June 10, 2014 11:55:04 AM UTC-7, Dale Worley wrote:
I think what will work is:
1) Find the first commit before the tag that has a different content
for the file:
$ git log -n 1 tagname^ -- filename
commit b3282e06e39e1ddaa44806eadbfac06a19fabe09
...
2) Find the SHA
From: John Fisher fishook2...@gmail.com
This is his complaint:
git ls-tree -r tagname
- snip -
100644 blob 990c3e0f7efc8ddf869dbb39ba0065c9e9578df4rmapi_bcmxlat.c
-snip-
root@oa4-hv-B1net:bcm# git log rmapi_bcmxlat.c | grep 990c3e0f7ef
There is no such SHA in git
10 matches
Mail list logo
