Hi Daniel,
On So, 18 Okt 2009, Daniel Barkalow wrote:
> > - how would one access this "sequence" number on the server
>
> There isn't currently anything built in that counts up like that; however,
> it shouldn't be too hard to add something, because the reflog gets an
> entry at the same times the sequence number would increase. In fact, you
Ok.
> > - is there a way to determine at which of this "sequence" numbers a specific
> > file has been changed last?
>
> There isn't a built-in way, but you can find the current hash for a
> filename with "git ls-tree -r <branch> <filename>", and find the hash as
> of N changes ago with "git ls-tree -r <branch>@{<N>} <filename>". You're
> looking for the smallest N where they don't match. (And you probably
> don't want to be a binary search or the like, because that might miss that
That sounds like we cannot use that, because we have to do that for about
80k files and that on each (at least daily) rebuilt. That is not feasable.
Again thanks for your helpful comments!
Norbert
-------------------------------------------------------------------------------
Dr. Norbert Preining Associate Professor
JAIST Japan Advanced Institute of Science and Technology preining@xxxxxxxxxxx
Vienna University of Technology preining@xxxxxxxx
Debian Developer (Debian TeX Task Force) preining@xxxxxxxxxx
gpg DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094
-------------------------------------------------------------------------------
BRUMBY
The fake antique plastic seal on a pretentious whisky bottle.
--- Douglas Adams, The Meaning of Liff
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html