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

Re: [PATCH] Don't propagate SKIPPED warning to future commits.

From
Junio C Hamano <junkio@cox.net>
Date
Feb 11, 2006, 02:21 UTC
Message-ID
<7vpslutz2t.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<87r76avfhz.wl%cworth@cworth.org>
Carl Worth <cworth@cworth.org> writes:
Show 9 quoted lines
> Here's a simple bug fix for the (currently undocumented) -S flag to
> git-cvsimport.
>
> The -S flag allows an import to proceed in the face of a missing ,v
> file in the CVS repository. It marks this by adding a SKIPPED warning
> in the relevant commit.
>
> Without this patch, the SKIPPED warning propagates to all future
> commits, (and accumulates with future SKIPPED warnings).

I might be missing something fundamental, but isn't prapagating the warning a good thing? If an earlier commit is suspected to lack some path that needs to be there (I think that is what "missing ,v file" means), wouldn't later commits built on top of that one be by definition missing that path?

Previous: Carl WorthNext: Carl Worth
Message 2 of 3 in “Don't propagate SKIPPED warning to future commits.”
  1. Don't propagate SKIPPED warning to future commits.Carl Worth, Feb 11, 2006
  2. Junio C HamanoFeb 11, 2006
  3. Carl WorthFeb 11, 2006

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.