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

[PATCH 00/10] Misc. cvsserver, dashless, and test suite patches

From
MOMatthew Ogilvie <mmogilvi_git@miniinfo.net>
Date
Jan 24, 2009, 23:43 UTC
Message-ID
<1232840601-24696-1-git-send-email-mmogilvi_git@miniinfo.net>

This series of small patches fixes a few minor issues I noticed while researching what it would take to for cvsserver to support cvs's "-r" flags properly. No real progress on the "-r" front, but see comments in the "cvsserver: add comments about database ..." email.

The "run test suite without dashed..." patch has wide scope, even though is is fairly small. It (along with fixing the things it found in t2300 and t3409) was inspired by a desire to avoid future regressions of the bug fixed in "cvsserver: run dashless 'git commands'" patch, where git-cvsserver was trying to run dashed commands that are not in the default PATH...

As this patch series was going to press, I noticed that the "run test suite without dashed..." patch probably conflicts with recently posted valgrind test suite patches. See extra comments in the email for possible resolutions.

The other patches in this series are mostly independent of each other.

When working on the "git-shell" patch, I noticed a couple of other things related to "git-shell" that maybe ought to be changed (change the argc==2 special case, and document the best way(s) to configure an account to use git-shell). See also extra information in the email.

-- Matthew Ogilvie [mmogilvi_git@miniinfo.net]

Matthew Ogilvie (10):
  cvsserver: removed unused sha1Or-k mode from kopts_from_path
  cvsserver: add comments about database schema/usage
  cvsserver: remove unused functions _headrev and gethistory
  git-shell: allow running git-cvsserver, not just cvs
  cvsserver: run dashless "git command"s to access plumbing
  t2300: use documented technique to invoke git-sh-setup
  t3409: use dashless "git commit" instead of "git-commit"
  run test suite without dashed git-commands in PATH
  Revert "adapt git-cvsserver manpage to dash-free syntax"
  cvsserver doc: emphasize using CVS_SERVER= phrase within CVSROOT
 .gitignore                        |    1 +
 Documentation/git-cvsserver.txt   |   29 +++++--
 Documentation/git-shell.txt       |    5 +-
 Makefile                          |   40 +++++++---
 git-cvsserver.perl                |  163 ++++++++++++++++---------------------
 shell.c                           |    1 +
 t/t2300-cd-to-toplevel.sh         |    2 +-
 t/t3409-rebase-preserve-merges.sh |    6 +-
 t/t9400-git-cvsserver-server.sh   |   88 ++++++++++++++++++++
 t/test-lib.sh                     |   14 +++-
 test-bin-wrapper.sh               |   12 +++
 11 files changed, 246 insertions(+), 115 deletions(-)
 create mode 100644 test-bin-wrapper.sh
Next: Matthew Ogilvie
Message 1 of 16 in “Misc. cvsserver, dashless, and test suite patches”
  1. 00/10 Misc. cvsserver, dashless, and test suite patchesMatthew Ogilvie, Jan 24, 2009
  2. 01/10 cvsserver: removed unused sha1Or-k mode from kopts_from_pathMatthew Ogilvie, Jan 24, 2009
  3. 02/10 cvsserver: add comments about database schema/usageMatthew Ogilvie, Jan 24, 2009
  4. 03/10 cvsserver: remove unused functions _headrev and gethistoryMatthew Ogilvie, Jan 24, 2009
  5. 04/10 git-shell: allow running git-cvsserver, not just cvsMatthew Ogilvie, Jan 24, 2009
  6. 05/10 cvsserver: run dashless "git command"s to access plumbingMatthew Ogilvie, Jan 24, 2009
  7. 06/10 t2300: use documented technique to invoke git-sh-setupMatthew Ogilvie, Jan 24, 2009
  8. 07/10 t3409: use dashless "git commit" instead of "git-commit"Matthew Ogilvie, Jan 24, 2009
  9. 08/10 run test suite without dashed git-commands in PATHMatthew Ogilvie, Jan 24, 2009
  10. 09/10 Revert "adapt git-cvsserver manpage to dash-free syntax"Matthew Ogilvie, Jan 24, 2009
  11. 10/10 cvsserver doc: emphasize using CVS_SERVER= phrase within CVSROOTMatthew Ogilvie, Jan 24, 2009
  12. Johannes SchindelinJan 25, 2009
  13. Matthew OgilvieJan 26, 2009
  14. Johannes SchindelinJan 26, 2009
  15. Matthew OgilvieJan 27, 2009
  16. Johannes SchindelinJan 25, 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.