> Can we provide a sequence of git commands for folks to run? Or will the
> official guidance be to create new local clones of each repo?
Yes, I will do that in the readme file placed on master branch, once cleaned up.
Don't panic, please. git is a wonderful version control system in that
it doesn't care where the "repository" comes from. It's just a graph
of commits - when we clone the repository, it remains the same graph.
Any commits (on your local branches) created prior to the fork ("PRs")
remain valid - the element of relative difficulty is in the github
interface, not in git itself...
Cross-project patches will not merge automatically - you'll have to
split them manually. But this, again, is something relatively trivial
(you could even edit the patch file with a text editor...).
Please don't rush to commit changes to the lucene-solr repository.
Dawid
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
