Duy Nguyen wrote:
> I wonder if we should make this "git/1.9.1" information more visible. We could
>
> 1) Always print it when cloning
> 2) Print it when cloning with -v (printing all capabilities with -v
> might not be a bad idea)
> 3) Include it in error messages when clone/fetch fails
I don't
Bob Proulx wrote:
> 17:20:40.590177 pkt-line.c:46 packet:clone<
> 34e7202270c381f4e5734180dc19426ce69f2e1e HEAD\0multi_ack thin-pack side-band
> side-band-64k ofs-delta shallow no-progress include-tag multi_ack_detailed
> symref=HEAD:refs/heads/master agent
am sure the file creation is there. Because it isn't being done
anywhere. But the problem is before that time period. By then the
paths are already set.
> >Bob Proulx wrote:
> >> git --version # from today's git clone build
> >> git version 2.11.0.485.g4e59
Hello Johannes,
Thank you very much for the good hints here. They are very helpful.
Johannes Schindelin wrote:
> Assuming that you can rebuild your Git with debug symbols and without
> optimization (simply remove the -O2 from CFLAGS in the Makefile, I never
> had any luck with single-stepping in
I am trying to understand a problem with shallow checkouts through the
git-daemon. The server side fails trying to create a shallow_XX
file in the repository. But of course it can't due to no permissions
from the git-daemon user.
However the problem driving me crazy is that this only fails t
5 matches
Mail list logo
