Eric S. Raymond wrote on Thu, Nov 29, 2012 at 00:59:45 -0500:
In summary, Subversion repository histories do not round-trip through
reposurgeon editing. File content changes are preserved but some
metadata is unavoidably lost. Furthermore, writing out a DVCS history
in Subversion also
On 29.11.2012 08:58, Daniel Shahaf wrote:
I think you're saying that adds might turn into copies, and
vice-versa. That is something users would notice --- it is certainly
exposed in the UI --- even though node-id's are not exposed to clients.
... yet. But there are plans underway to expose
Daniel Shahaf danie...@elego.de:
Subversion's metadata doesn't have separate author and committer
properties, and doesn't store anything but a Unix user ID as
attribution. I don't see any way around this.
You're not fully informed, then.
1) svn:author revprops can contain any UTF-8
(note, other half of the thread is on dev@svn only..)
Eric S. Raymond wrote on Thu, Nov 29, 2012 at 06:46:37 -0500:
Daniel Shahaf danie...@elego.de:
You might also seek community consensus to reserve an svn:foo name for
the original author property --- perhaps svn:original-author --- so
Daniel Shahaf danie...@elego.de:
I don't see the kludge here --- git has a author != committer
distinction, svn doesn't, so if you want to grow that distinction the
most natural way is a new property. Storing additional information in
svn:author is a separate issue.
See my advocacy to Branko
Hi,
Von: Eric S. Raymond [mailto:e...@thyrsus.com]
How does reposurgeon handle empty directories with (node) properties?
Currently by ignoring all of them except svn:ignore, which it turns
into .gitignore content on the gitspace side. And now vice-versa, too.
Not clear what else it
This is something that probably doesn't happen very often -
cross-posting to the Subversion and git dev lists that is on-topic for
both :-).
The repo head version of reposurgeon can now write Subversion
repositories from its common git-import-stream-based representation of
repository histories,
7 matches
Mail list logo
