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

Re: GSOC Proposal draft: git-remote-svn

From
ASAndrew Sayers <andrew-git@pileofstuff.org>
Date
Apr 14, 2012, 22:57 UTC
Message-ID
<4F8A00BE.6020409@pileofstuff.org>
In-Reply-To
<1533147.bdVc1SQHSj@flomedio>
On 11/04/12 20:09, Florian Achleitner wrote:
> Furthermore the remote-helper has no way of asking the user something, right?
> So it can only fail if something is ambigous in the svn repository layout. So 
> I thought the SBL is exactly to describe these cases, and that's what I need.
Sorry, I missed this when it was first posted.

I'm not sure whether the remote helper is allowed to ask the user things, but there can be times when that would be helpful. The one that jumps to mind is tag handling.

SVN considers tags and branches to be functionally identical, whereas git likes to create "annotated tags" (commits with a special tag message on top of the normal commit message) that can't be changed once they've been created. So if e.g. a tag is created then later committed to again, what do you do? Do you refuse to make annotated tags in case you need to change them later? Do you ignore later commits so that annotated tags work nicely?

SBL can't provide much help here, as a tag could be created in one update, then committed to again in another update. Last time this was discussed[1], the consensus seemed to be that there any clever solution would drive straight past "it just works" into "why did it do that?" territory, so the only sensible solution would be to ask what to do.

As I say, I don't really know anything about remote helpers, but I'd be very surprised if you weren't allowed to at least fail with a message like "Please set svn.tagStrategy, see `man git-config` for details".

	- Andrew
[1]http://thread.gmane.org/gmane.comp.version-control.git/192106/focus=192286
Previous: Florian AchleitnerNext: Jakub Narebski
Message 28 of 46 in “GSoC intro”
  1. Florian AchleitnerMar 19, 2012
  2. Andrew SayersMar 19, 2012
  3. Florian AchleitnerMar 20, 2012
  4. David BarrMar 20, 2012
  5. Florian AchleitnerMar 21, 2012
  6. Ramkumar RamachandraMar 26, 2012
  7. Florian AchleitnerMar 27, 2012
  8. GSOC Proposal draft: git-remote-svnFlorian Achleitner, Apr 2, 2012
  9. Ramkumar RamachandraApr 2, 2012
  10. Jonathan NiederApr 2, 2012
  11. Jonathan NiederApr 2, 2012
  12. Florian AchleitnerApr 3, 2012
  13. Jonathan NiederApr 3, 2012
  14. Tomas CarneckyApr 5, 2012
  15. Andrew SayersApr 2, 2012
  16. Jonathan NiederApr 2, 2012
  17. Andrew SayersApr 2, 2012
  18. Jonathan NiederApr 3, 2012
  19. Andrew SayersApr 3, 2012
  20. Jonathan NiederApr 3, 2012
  21. Florian AchleitnerApr 5, 2012
  22. Dmitry IvankovApr 5, 2012
  23. Stephen BashApr 9, 2012
  24. Jonathan NiederApr 10, 2012
  25. Andrew SayersApr 10, 2012
  26. Jonathan NiederApr 10, 2012
  27. Florian AchleitnerApr 11, 2012
  28. Andrew SayersApr 14, 2012
  29. Jakub NarebskiApr 11, 2012
  30. Jonathan NiederApr 11, 2012
  31. Florian AchleitnerApr 11, 2012
  32. Dmitry IvankovApr 11, 2012
  33. Jonathan NiederApr 11, 2012
  34. Andrew SayersApr 11, 2012
  35. Thomas RastApr 12, 2012
  36. Florian AchleitnerApr 12, 2012
  37. Andrew SayersApr 12, 2012
  38. Florian AchleitnerApr 14, 2012
  39. Andrew SayersApr 14, 2012
  40. Stephen BashApr 15, 2012
  41. Jonathan NiederApr 13, 2012
  42. Florian AchleitnerApr 14, 2012
  43. Florian AchleitnerApr 18, 2012
  44. Florian AchleitnerApr 19, 2012
  45. Miles BaderMar 28, 2012
  46. Dmitry IvankovMar 28, 2012

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.