Re: Hash algorithm analysis

On Sun, 22 Jul 2018 14:21:48 +, brian m. carlson wrote: > On Sun, Jul 22, 2018 at 11:34:42AM +0200, Eric Deplagne wrote: > > On Sat, 21 Jul 2018 23:59:41 +, brian m. carlson wrote: > > > I don't know your colleagues, and they haven't commented here. One > > >

Re: Hash algorithm analysis

hes accordingly. The community is free, as > always, to reject my patches if taking them is not in the interest of > the project. > > [0] > https://public-inbox.org/git/CAL9PXLzhPyE+geUdcLmd=pidt5p8efebbsgx_ds88knz2q_...@mail.gmail.com/ > -- > brian m. carlson: Houston, Texas, US > OpenPGP: https://keybase.io/bk2204 -- Eric Deplagne signature.asc Description: Digital signature

Re: unable to pull from remote if commit date is in the future

ult, which might be different than the committer > date. The "-40643156" timezone definitely looks suspicious, though. I'm > curious if it is bad handling in the time code, or if the commit has > corrupt ident lines. > > -Peff 2106 is the year of unsigned 32-bit unix time bug, would there be any relation ? -- Eric Deplagne signature.asc Description: Digital signature

Re: Minor Bug in Renaming Branches

ANCH^ >> git rev-parse BRANCH >> (I'd expect BRANCH^ as return) >> >> (I don't have a windows machine for testing here, so that >> is pure speculation) >> > Yes, another reason not to use branch and BRANCH in the same repo. > (You can test under Linux &

Re: Merge conflicts are reported relative to root not cwd

know which file it is talking about. From my use of git, I'd really love to be able to copy/paste ../../../../../../builtin/fetch.c to some vi (or anything else) command line instead of having vi (or whatever) bark that it does not know where builtin/fetch.c is. -- Eric Deplagne signature.asc Description: Digital signature