git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Protocol v2: The wrong --shallow-since time format causes git to wait indefinitely

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 13, 2019, 03:42 UTC
Message-ID
<xmqqpnhwbfx7.fsf@gitster-ct.c.googlers.com>
In-Reply-To
<tencent_AB1A7466D1F2EF9A84B437705F06A7652709@qq.com>
"Force.Charlie" <force@forcemz.net> writes:
> # time format wrong
> git -c protocol.version=2 clone https://github.com/git/git.git --shallow-since=20151012

That's the valid/right way to specify the timestamp that is 20,151,012 seconds after the epoch (i.e. 1970-01-01), isn't it?

Previous: Force.CharlieNext: Denton Liu
Message 2 of 4 in “Protocol v2: The wrong --shallow-since time format causes git to wait indefinitely”
  1. Force.CharlieNov 13, 2019
  2. Junio C HamanoNov 13, 2019
  3. Denton LiuNov 19, 2019
  4. Denton LiuNov 19, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.