blocks|key|1091591|text|如果您的历史记录中实际上缺少修订(从您的问题中不能完全清楚实际上缺少了什么)，并且只有一个月左右，那么您可能还有时间--看看reflog；它保留了您签出的每个引用的副本，所以如果您犯了错误，您可以找回以前的引用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1091592|默认情况下，reflog条目保留90天，它们将在git+gc过期。|offset|length|style|CODE|1091593|git+help+reflog|code-block|syntax|javascript|1091594|entityMap^0|0|O|6|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

If you're actually missing revisions from your history (it's not completely clear from your question what's actually missing) and it's only been around a month, you probably still have time -- look at the reflog; it keeps a copy of every reference you have checked out, so if you make a mistake you can get back what you had before.

The default is to keep reflog entries for 90 days, they are expired by <code>git gc</code>.

<pre><code>git help reflog
</code></pre>

blocks|key|877017|text|我会运行一个遍历所有对象的脚本。您需要先解压缩所有的包文件。脚本将检查类型，如果是提交，您将看到您是否是作者。然后检查日期。列出它们，并使用grep表示所需的文件名。完成感兴趣的提交后，使用以下命令创建分支|type|unstyled|depth|inlineStyleRanges|entityRanges|data|877018|git+branch+RecoveredWork+hash-of-your-commit|code-block|syntax|javascript|877019|看看你是否得到了你想要的一切|877020|git+log+RecoveredWork+--graph+--decorate|877021|从这里，你可能想要做一些过滤器分支，移植和/或重新建立基础，以再次链接历史。|877022|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I would run a script that goes through all the objects. You would need to unpack all the pack files first. The script would check the type, if it is a commit you would see if you are the author. Then check the date. List those and grep for the file name that you want. Once you have the commit of interest, create a branch with

<pre><code>git branch RecoveredWork hash-of-your-commit
</code></pre>

and see if you have all that you want with

<pre><code>git log RecoveredWork --graph --decorate
</code></pre>

from here you may want to do some filter branching, grafting and/or rebasing to link up the history again.

blocks|key|877081|text|在Git中没有文件移动的概念。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|877082|一些工具，如GitHub，考虑将包含已删除的名为X的文件和已创建的名为X的文件的提交视为文件移动。|877083|根据Linus+Torvalds的说法，文件移动只是重构的一个特例；因此Git不会区别对待它。这种特殊情况的处理，就像许多其他情况一样，留给了更高级别的工具(比如前端)。|877084|有关此主题的更多信息，请查看Linus+Torvalds的this+answer。|offset|length|877085|entityMap|0|LINK|mutability|MUTABLE|url|https://public-inbox.org/git/Pine.LNX.4.58.0504141102430.7211@ppc970.osdl.org/^0|0|0|0|T|B|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@$H|V|I|W|1|X]]|A|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

In Git there's no the concept of file move.

Some tools, like GitHub, consider a commit containing a file named X that has been deleted and a file named X that has been created a file move.

According to Linus Torvalds, file move is just a special case of refactoring; for this reason Git will not treat it differently. Handling of this special case, like many others, is left to higher-level tools (such as frontends).

For more info on this topic, check <a href="https://public-inbox.org/git/Pine.LNX.4.58.0504141102430.7211@ppc970.osdl.org/" rel="nofollow noreferrer">this answer</a> from Linus Torvalds.

blocks|key|877141|text|在我看来，你想要的是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|877142|git+log+--follow+some_file.cpp|code-block|syntax|javascript|877143|详情请参见http://git-scm.com/docs/git-log。我不确定这是不是你想要的；但是对于git来说，git跟踪的是内容而不是文件。问题是，确定信息真的很昂贵，并且假设通常情况下你不需要它。|offset|length|877144|entityMap|0|LINK|mutability|MUTABLE|url|http://git-scm.com/docs/git-log^0|0|0|5|V|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

As far as I see it you want:

<pre><code>git log --follow some_file.cpp
</code></pre>

See <a href="http://git-scm.com/docs/git-log" rel="nofollow">http://git-scm.com/docs/git-log</a> for details. I am not sure if that is what you want; but in case of git, git tracks content not files. The problem is that determining that information is really expensive and it is assumed that normally you don't need it...

blocks|key|1091845|text|我能想到几种可能性。如果事情只是被打乱，但没有跟踪，那么我假设这是在两个不同的提交中完成的……一个要删除，另一个要重新添加。在之前的提交中创建一个新的分支，将接下来的两个提交加载为一个提交，然后附加之后的所有内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1091846|如果不是这样，您可能需要使用git+log+-M+-C查看提交|offset|length|style|CODE|1091847|entityMap^0|0|E|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

I can think of a few possibilities. If things were just shuffled around, but don't track, then I presume that this was done in two different commits... one to remove and then one to re-add. Create a new branch in the commit before that, load in the next two commits as one commit, and then append everything after that.

If that is not the case, you may need to look at the commits with <code>git log -M -C</code>

I made a commit about a month ago that involved me creating new folder and sub-folders and moving my source code files in between them. I just was looking through my history for the first time since then and realized git has 'lost' history since the original files were deleted and then re-added, I suppose - i.e. when I'm viewing a file in my git GUI (it's under NDA so I can't discuss it directly, but for example, this repository is broken on GitHub too. GitHub clearly shows its detecting the commit as a series of moves.) it only shows history for each file back to when the project folder was reorganized.

After reading a few questions ( <a href="https://stackoverflow.com/questions/1430749/getting-git-to-acknowledge-previously-moved-files">Getting Git to Acknowledge Previously Moved Files</a>, <a href="https://stackoverflow.com/questions/433111/how-to-make-git-mark-a-deleted-and-a-new-file-as-a-file-move">How to make git mark a deleted and a new file as a file move?</a>), I'm simply more lost than when I started. It sounds like from those answers that I won't be able to fix this at all? I'd really appreciate any help here.

Lost git history after reorganizing project folder

GitHub

我在一个月前做了一个提交，包括创建新的文件夹和子文件夹，并在它们之间移动我的源代码文件。从那时起，我第一次浏览了我的历史记录，意识到git已经“丢失”了历史记录，因为原始文件被删除了，然后又重新添加了，我想--也就是当我在git GUI中查看文件的时候(它在保密协议下，所以我不能直接讨论它，但例如，这个存储库在GitH...

问重新组织项目文件夹后丢失git历史记录
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问重新组织项目文件夹后丢失git历史记录EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问重新组织项目文件夹后丢失git历史记录
EN