> I would actually call that behaviour a bug.
Well, yes, that was my inclination, too. But writing documentation was
easier than writing a code patch. :-)
Even when it is fixed, a comment about when it was fixed and what the
buggy version did should live in the BUGS section for a while, to warn
"George Spelvin" writes:
> Try the following commands in an empty directory:
> (I'm using the bash extention for {1..5}.)
>
> git init
> for i in {1..5}; do git commit -m "Commit $i" --allow-empty; done
> git reflog
> bc93e06 HEAD@{0}: commit: Commit 5
> e14f92d HEAD@{1}: commit: Comm
Try the following commands in an empty directory:
(I'm using the bash extention for {1..5}.)
git init
for i in {1..5}; do git commit -m "Commit $i" --allow-empty; done
git reflog
bc93e06 HEAD@{0}: commit: Commit 5
e14f92d HEAD@{1}: commit: Commit 4
ac64d8e HEAD@{2}: commit:
3 matches
Mail list logo
