Am 04.12.14 21:18, schrieb Junio C Hamano:
> Jonathan Nieder writes:
>> Could you make a test script that illustrates and reproduces the
>> problem? I.e., a patch to a file like t/t1410-reflog.sh, such that
>> if I run
>>
>> cd git
>> make
>> cd t
>> ./t1410-reflog.sh
>>
>> th
Hi Jonathan,
Am 02.12.14 00:35, schrieb Jonathan Nieder:
> Christoph Mallon wrote:
>> % git rev-parse 'master@{52}'
>> warning: Log for ref refs/heads/master has gap after Thu, 1 Jan 1970
>> 00:00:01 +.
>> 0036
>
Am 01.12.14 19:53, schrieb Stefan Beller:
> So I am running a 3.13.0-40-generic x86_64 linux (so its's amd64) and
> git version 2.1.2
> and I cannot reproduce the bug you are describing. :(
):
I can reproduce it with
* OS X, i386 binary, git 2.2.0
* FreeBSD, amd64, git 2.1.0 and up (bisected it t
This commit seems to introduce the bug:
4207ed285f31ad3e04f08254237c0c1a1609642b
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
I encountered a strange bug concerning the reflog.
I suspect some kind of out-of-bounds access.
The symptom is:
%git rev-parse 'master@{52}'
warning: Log for ref refs/heads/master has gap after Thu, 1 Jan 1970
00:00:01 +.
0036
Try the following:
git i
Hi,
if I run rebase --continue (e.g. after a conflict resolution), then the rebase
always ends with this error message:
It seems that there is already a rebase-apply directory, and
I wonder if you are in the middle of another rebase. If that is the
case, please try
6 matches
Mail list logo
