2014-11-10 12:56 GMT+01:00 Baruch Burstein <bmburst...@gmail.com>:
> Any changes done outside of the trunk/branches/tags directories will be
> ignored (silently or with a warning)
OK
> A branch/tag that doesn't have an obvious parent checkin to apply to, will
> be applied to the most recent checkin (or should it be the most recent one
> on the trunk?)
No opinion on this one.
> If a single commit has multiple tags/branches/trunk changes, they will each
> get recorded separately, but with the same timestamp and svn-revision-NNN
> tag.
Big YES here.
> If a change is made to a file under the tags directory, or a file is
> added/deleted, the commit that it tagged will be forked (or should it
> branch?) and a new commit with the changes will be added and tagged.
Should be a branch with branch-name "svn-rev-NNN", which is a tag
at the same time.
> If a branch is deleted, it will be marked as closed.
OK
> If the trunk is deleted, the whole thing will fail.
I would prefer to close the trunk and go on. Fossil works fine without trunk ;-)
Most likely, next commit a new "trunk" will be committed (this is
exactly what commits 71 ans 72 of tkimg do .....) ;-)
> I don't know how to manage deleted tags.
This should result in a control artifact in stead of a commit, which
simply deletes the tag from the referenced commit.
> How does that sound?
> If it is all right, it will still take a few days to put this together.
Looks fine to me, I hope my remarks above make sense.
Thanks for your great work! Allowing a single SVN commit to
result in multiple fossil commit should be enough to get
tkimg commit 70 working.
Regards,
Jan Nijtmans
_______________________________________________
fossil-dev mailing list
fossil-dev@lists.fossil-scm.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/fossil-dev
