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

Re: [RFC 00/11] Foreign VCS helper program for CVS repositories

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Jul 27, 2009, 17:27 UTC
Message-ID
<alpine.LNX.2.00.0907271251280.2147@iabervon.org>
In-Reply-To
<1248656659-21415-1-git-send-email-johan@herland.net>
On Mon, 27 Jul 2009, Johan Herland wrote:
Show 9 quoted lines
> This series is a first draft towards implementing a foreign VCS helper
> program for CVS.
> 
> It is based on the 'db/foreign-scm' and 'jh/notes' topics in 'pu'. As such,
> this patch series should apply cleanly to current 'pu'.
> 
> The first 4 patches supply the necessary parts of Daniel Barkalow's
> foreign-scm topic that has not yet been merged to 'pu' (i.e. everything
> remaining in Daniel's original patch series, except the p4-specific stuff).

I've got some changes to this series in the works; I just made a few changes to share the transport-side code for interacting with the helper with the transport-side code for interacting with native-object helpers. Mainly, this means starting each line in the "list" response with "?" to indicate that you don't know the hash, since the protocol is trying to be compatible with cases where you do know.

Show 7 quoted lines
> The next 2 patches add some functionality to git fast-import, for
> facilitating the import of 'notes' objects (this is a _much_ faster way to
> generate/import notes than invoking "git notes edit -m MSG" for each note).
> 
> Next, there are 3 patches tweaking and expanding the git-vcs API (with
> corresponding implementations in the foreign transport code) to adjust for
> the CVS helper's needs.

These make sense to me. I assume you're planning to support exporting in some ways, but haven't got it working yet? I largely ignored the capabilities stuff because I didn't have two systems with differing requirements to actually use it.

	-Daniel
*This .sig left intentionally blank*
Previous: Johan HerlandNext: Johan Herland
Message 28 of 30 in “[RFC 00/11] Foreign VCS helper program for CVS repositories”
  1. Johan HerlandJul 27, 2009
  2. 01/11 Add specification of git-vcs-* helper programsJohan Herland, Jul 27, 2009
  3. 02/11 Use a function to determine whether a remote is validJohan Herland, Jul 27, 2009
  4. 03/11 Allow programs to not depend on remotes having urlsJohan Herland, Jul 27, 2009
  5. Junio C HamanoJul 27, 2009
  6. Daniel BarkalowJul 27, 2009
  7. Alex RiesenJul 29, 2009
  8. Johan HerlandJul 30, 2009
  9. 04/11 Add a transport implementation using git-vcs-* helpersJohan Herland, Jul 27, 2009
  10. 05/11 Refactor path name parsing into new function: get_path_str()Johan Herland, Jul 27, 2009
  11. 06/11 Add support for mark references as path namesJohan Herland, Jul 27, 2009
  12. Shawn O. PearceJul 27, 2009
  13. Johan HerlandJul 27, 2009
  14. Shawn O. PearceJul 27, 2009
  15. 06/11 fast-import: Add support for importing commit notesJohan Herland, Jul 28, 2009
  16. Junio C HamanoJul 29, 2009
  17. Johan HerlandJul 29, 2009
  18. Shawn O. PearceJul 29, 2009
  19. Junio C HamanoJul 29, 2009
  20. Johan HerlandJul 30, 2009
  21. Junio C HamanoJul 30, 2009
  22. Junio C HamanoJul 29, 2009
  23. Johan HerlandJul 29, 2009
  24. 07/11 Preliminary clarifications to git-vcs documentationJohan Herland, Jul 27, 2009
  25. 08/11 Teach foreign transport code to perform the "capabilities" commandJohan Herland, Jul 27, 2009
  26. 09/11 Introduce a 'marks <filename>' feature to the foreign transport codeJohan Herland, Jul 27, 2009
  27. 11/11 Add simple test cases of git-vcs-cvs functionalityJohan Herland, Jul 27, 2009
  28. Daniel BarkalowJul 27, 2009
  29. Johan HerlandJul 27, 2009
  30. Daniel BarkalowJul 27, 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.