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

Re: git-svn and svn properties on upstream

From
Avery Pennarun <apenwarr@gmail.com>
Date
Jul 12, 2008, 21:30 UTC
Message-ID
<32541b130807121430ia85a3c8u3efc0b5a8591eb44@mail.gmail.com>
In-Reply-To
<608871.39190.qm@web27807.mail.ukl.yahoo.com>
On 7/12/08, Paul Talacko <gnuruandstuff@yahoo.co.uk> wrote:
Show 5 quoted lines
>  * amend SVN::Git::Editor::generate_diffs to add another hash key to amend properties.
>  * look for ~/.subversion/config or /etc/subversion/config to see whether auto-props are set
>  * if set, set the properties accordingly in the @mods array of hashes.
>  * SVN::Git::Editor::A then sets the properties according to the contents of the $mods hash
> ref, using set_file_prop().

This sounds like it would be fine for almost all users. Specifically me :) I think it's a good starting point, so you could build something even more flexible on top later if you wanted.

I guess in an ideal world there'd be a way to track svn properties in the git history, but I have no idea where such things should probably go.

Have fun,
Avery
Previous: Paul TalackoNext: Peter Harris
Message 2 of 3 in “git-svn and svn properties on upstream”
  1. Paul TalackoJul 12, 2008
  2. Avery PennarunJul 12, 2008
  3. Peter HarrisJul 13, 2008

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.