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

Re: [PATCH] cvsimport: skip commits that are too recent

From
Martin Langhoff <martin.langhoff@gmail.com>
Date
Jan 8, 2007, 03:18 UTC
Message-ID
<46a038f90701071918y4a8078can90ae69dd1d9f9ffd@mail.gmail.com>
In-Reply-To
<7vd55qz2d1.fsf@assigned-by-dhcp.cox.net>
On 1/8/07, Junio C Hamano <junkio@cox.net> wrote:
> Well I meant to say that my conclusion is that that flag is not
> needed in practice.
you are getting soft in your old age, man :-)

More seriously, as soon as I sent the patch I thought of the use case you describe. Not everyone is as patient as you are, and someone may have things scripted. If the cvs repo is local/fast and under your control, it doesn't make sense to be _so_ conservative.

Also -- by having the flag we get an excuse to mention it in the doco.
m
Previous: Junio C Hamano
Message 5 of 5 in “cvsimport: skip commits that are too recent”
  1. cvsimport: skip commits that are too recentMartin Langhoff, Jan 8, 2007
  2. Junio C HamanoJan 8, 2007
  3. Martin LanghoffJan 8, 2007
  4. Junio C HamanoJan 8, 2007
  5. Martin LanghoffJan 8, 2007

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.