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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Protocol v2: The wrong --shallow-since time format causes git to wait indefinitely
From: Junio C Hamano <gitster@xxxxxxxxx>
Date: Wed, 13 Nov 2019 12:42:28 +0900
Cc: "git" <git@xxxxxxxxxxxxxxx>
In-reply-to: <tencent_AB1A7466D1F2EF9A84B437705F06A7652709@qq.com> (Force Charlie's message of "Wed, 13 Nov 2019 09:00:52 +0800")
References: <tencent_AB1A7466D1F2EF9A84B437705F06A7652709@qq.com>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux)

"Force.Charlie" <force@xxxxxxxxxxx> 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?

Follow-Ups:
- Re: Protocol v2: The wrong --shallow-since time format causes git to wait indefinitely
  - From: Denton Liu

References:
- Protocol v2: The wrong --shallow-since time format causes git to wait indefinitely
  - From: =?gb18030?b?Rm9yY2UuQ2hhcmxpZQ==?=

Prev by Date: Re: [PATCH 1/2] clone: remove fetch_if_missing=0
Next by Date: Re: [PATCH 1/1] contrib: Add --recursive flag for bash completion
Previous by thread: Protocol v2: The wrong --shallow-since time format causes git to wait indefinitely
Next by thread: Re: Protocol v2: The wrong --shallow-since time format causes git to wait indefinitely
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux