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

Re: [PATCH] git-cvsserver: handle CVS 'noop' command.

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 29, 2009, 23:46 UTC
Message-ID
<7vhc3hd6ba.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<d4bc1a2a0901291539m636f0fc8s5d9280ce9b7d22b2@mail.gmail.com>
Stefan Karpinski <stefan.karpinski@gmail.com> writes:
Show 9 quoted lines
> So apparently a response *is* expected. I'm not really familiar enough
> with CVS or git-cvsserver to determine what that means it should do,
> but I suspect from perusing the code that req_EMPTY is the appropriate
> action.
>
> Moreover, I've moved on from using git-cvsserver myself, having
> instead convinced my Windows-using compatriots to use msysgit instead.
> So if you feel that this change is unwarranted, feel free to just drop
> it.

Because the issue currently has our attention, and we think we know that the code does not do the right thing currently, and that we are fairly sure that the right thing is to do req_EMPTY, I'd rather see a tested fix applied so that we can forget about it ;-)

It's good that you moved your people to native git environment, but if you have an environment where you can test the fix still lying around, I'd appreciate a quick test and resubmit.

Previous: Stefan KarpinskiNext: Stefan Karpinski
Message 10 of 12 in “Re: [PATCH] git-cvsserver: run post-update hook *after* update.”
  1. Stefan KarpinskiJan 23, 2009
  2. Junio C HamanoJan 23, 2009
  3. git-cvsserver: run post-update hook *after* update.Stefan Karpinski, Jan 29, 2009
  4. Junio C HamanoJan 29, 2009
  5. Stefan KarpinskiJan 29, 2009
  6. Andy ParkinsJan 29, 2009
  7. git-cvsserver: handle CVS 'noop' command.Stefan Karpinski, Jan 29, 2009
  8. Junio C HamanoJan 29, 2009
  9. Stefan KarpinskiJan 29, 2009
  10. Junio C HamanoJan 29, 2009
  11. git-cvsserver: handle CVS 'noop' command.Stefan Karpinski, Jan 30, 2009
  12. Martin LanghoffJan 30, 2009

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.