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

Re: [PATCH] cvsserver: Fix handling of diappeared files on update

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Apr 11, 2007, 21:39 UTC
Message-ID
<Pine.LNX.4.64.0704111737180.27922@iabervon.org>
In-Reply-To
<7v1wiqoaph.fsf@assigned-by-dhcp.cox.net>
On Wed, 11 Apr 2007, Junio C Hamano wrote:
Show 35 quoted lines
> Frank Lichtenheld <frank@lichtenheld.de> writes:
> 
> > Only send a modified response if the client sent a
> > "Modified" entry. This fixes the case where the
> > file was locally deleted on the client without
> > being removed from CVS. In this case the client
> > will only have sent the Entry for the file but nothing
> > else.
> >
> > Signed-off-by: Frank Lichtenheld <frank@lichtenheld.de>
> > ---
> >  git-cvsserver.perl |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> >
> >  We really, really need a test suite for cvsserver...
> >  I've tested this as good for regressions as I could
> >  think of but am still unsure about it.
> >
> > diff --git a/git-cvsserver.perl b/git-cvsserver.perl
> > index 68aa752..25816c5 100755
> > --- a/git-cvsserver.perl
> > +++ b/git-cvsserver.perl
> > @@ -843,6 +843,7 @@ sub req_update
> >          if ( defined ( $wrev )
> >               and defined($meta->{revision})
> >               and $wrev == $meta->{revision}
> > +             and defined($state->{entries}{$filename}{modified_hash})
> >               and not exists ( $state->{opt}{C} ) )
> >          {
> >              $log->info("Tell the client the file is modified");
> > -- 
> > 1.5.1
> 
> This would make the modified response go away, but would it
> cause a fresh re-checkout to happen?

It falls through into the appropriate case, evidently. At least, it seems to resolve my issue.

	-Daniel
*This .sig left intentionally blank*
Previous: Junio C HamanoNext: Frank Lichtenheld
Message 6 of 9 in “cvsserver bug”
  1. Daniel BarkalowApr 11, 2007
  2. Frank LichtenheldApr 11, 2007
  3. cvsserver: Fix handling of diappeared files on updateFrank Lichtenheld, Apr 11, 2007
  4. Junio C HamanoApr 11, 2007
  5. Junio C HamanoApr 11, 2007
  6. Daniel BarkalowApr 11, 2007
  7. Frank LichtenheldApr 11, 2007
  8. Martin LanghoffApr 11, 2007
  9. Daniel BarkalowApr 11, 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.