Yeah, I think the svn interface is just a view of the git repo, so commits
are commits, whether they came in from svn or git. My assumption is that
with the svn interface, you're checking out from a single branch (e.g.
master), and that each svn commit is equivalent to a git commit + push.
Commits are going to come in the order they come in, and svn will see them
in that order. Commit date is less important in git because each commit
links explicitly to its parent(s).
We could use the svn rev numbers, but I don't think that's as good, because
we'll need to link to the commit referenced by that rev, and I'm not at all
sure you can do that with the svn rev numbers. In any case, the Guidelines
rev link is a solved problem—I fixed it months ago so that I could build my
own copy of the Guidelines out of my git-svn copy. If you're building out
of git, it should just work (with the proviso that my own copy of the repo
is hard-coded right now—we'll have to change that of course).
On Sun, Aug 2, 2015 at 10:40 PM, Martin Holmes
On 15-08-02 02:12 PM, Lou Burnard wrote:
Is it possible to have a single repo on GitHub, and simultaneously
access it through git and svn? That seems very unlikely.
Likely or not, that's what I currently do with the Stylesheets repo. And several others. As I remarked several days ago.
Ah, I didn't realize. So if I commit through the svn interface, and you commit through git, it's just handled automatically?
In that case, what happens in the case where you do several commits in git, but then do a single push? Is that one commit to the svn interface, or are they all separate? It's conceivable that commits from git that predate commits in svn would be pushed up after the svn commits.
If that all works nicely, though, then we don't have to make a decision about svn or git at all; people who like svn can use that, and people who like git can use that. The svn rev numbers will presumably still be sequential, so we can use that feature of svn rather than the git hashes for things like footers in the Guidelines, and we can mostly get by just by changing URLs. Nice.
Cheers, Martin
-- tei-council mailing list tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council
PLEASE NOTE: postings to this list are publicly archived