8/31/2023 0 Comments Git blameIf you try to pass a revision while using -contents, you get the following error: fatal: cannot use -contents with final commit object name The -contents option always blames the file as if it was based on the current HEAD commit. This option has been supported since 1cfe773 ( git-blame: no rev means start from the working tree file.,, Git v1.5.0-rc4 - merge) (" git-blame: no rev means start from the working tree file.") This is akin to copying the contents into the working tree and then running git blame. The -contents option can be used with git blame ( man) to blame the file as if it had the contents from the specified file. (Merged by Junio C Hamano - gitster - in commit 62df03c, ) blame: allow -contents to work with non-HEAD commit See commit 1a3119e () by Jacob Keller ( jacob-keller). Keeping such parent blobs in memory seems like a reasonable optimization that should incur additional memory pressure mostly when processing the merges from old branches.īefore Git 2.41 (Q2 2023), " git blame -contents= -``" ( man) used to be forbidden, but now it finds the origins of lines starting at contents through the history that leads to. When a parent blob already has chunks queued up for blaming, dropping the blob at the end of one blame step will cause it to get reloaded right away, doubling the amount of I/O and unpacking when processing a linear history. (Merged by Junio C Hamano - gitster - in commit 4d8c4da, ) blame.c: don't drop origin blobs as eagerly See commit f892014 () by David Kastrup ( fedelibre). with Git 2.22 (Q2 2019), will do so faster, because of a performance fix around " git blame", especially in a linear history (which is the norm we should optimize for). The git blame command annotates lines with information from the revision which last modified the line, and.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |