Junio C Hamano gits...@pobox.com writes:
Roberto Tyley roberto.ty...@gmail.com writes:
On 21/09/2013 23:16, Keshav Kini wrote:
[SNIP]
This situation came about because the BFG Repo-Cleaner doesn't write new
reflog entries after creating its new objects and moving refs around.
True enough -
Roberto Tyley roberto.ty...@gmail.com writes:
On 21/09/2013 23:16, Keshav Kini wrote:
[SNIP]
This situation came about because the BFG Repo-Cleaner doesn't write new
reflog entries after creating its new objects and moving refs around.
True enough - I don't think the BFG does write new
Junio C Hamano gits...@pobox.com writes:
Roberto Tyley roberto.ty...@gmail.com writes:
On 21/09/2013 23:16, Keshav Kini wrote:
[SNIP]
This situation came about because the BFG Repo-Cleaner doesn't write new
reflog entries after creating its new objects and moving refs around.
True enough
On 21/09/2013 23:16, Keshav Kini wrote:
[SNIP]
This situation came about because the BFG Repo-Cleaner doesn't write new
reflog entries after creating its new objects and moving refs around.
True enough - I don't think the BFG does write new entires to the
reflog when it does the final
Hello,
When trying out Roberto Tyley's BFG Repo-Cleaner program [1], I managed
to put a git repository in the following state:
[2] fs@erdos /tmp/bfg-test-repo $ cat .git/logs/HEAD
00afb9f9a0c87dba4a203413358984e9f4fa5ffb Keshav Kini
Keshav Kini keshav.k...@gmail.com writes:
For example, if `git
reflog show HEAD` displayed this:
0123456 [stuff] foo
789abcd [stuff] bar
ef01234 [stuff] baz
Then I would expect the reflog data file for HEAD to look something like
this, where '.' represents an unknown hex
6 matches
Mail list logo
