You could try: git clone https://github.com/TEIC/Guidelines.git https://github.com/TEIC/Guidelines.git cd Guidelines git checkout P5-Pure copy your changes into Guidelines/ in the right spot. If you have any new files: git add path/to/new/file git commit -am "What I did on my summer vacation." git push origin P5-Pure All done! See also https://github.com/TEIC/Guidelines-TEST/blob/master/README.md https://github.com/TEIC/Guidelines-TEST/blob/master/README.md and let me know where it fails to elucidate what’s going on. Basically, git clone == svn checkout; git add == svn add; git commit + git push == svn commit. The main difference being that you have a full copy of the repo locally, so you have an extra step of syncing your local repo with the remote repo.
On Aug 29, 2015, at 11:56 , Lou Burnard
wrote: You know those cartoons where the human is talking to the cat? and the cat hears only the word "food"? "clone", "commit and push" don't mean a lot to the unregenerate svn user.
On 29/08/15 16:22, Hugh Cayless wrote:
You could just clone the git repo, checkout the pure branch, copy your changes over, commit and push :-)
Happy to help if you need advice on doing so. It’d be a good test of the new repo.
On Aug 29, 2015, at 7:30 , Lou Burnard
wrote: On 26/08/15 14:17, Hugh Cayless wrote:
The tickets are not frozen, and are not moving yet (I just filed a bug!). The repo is the only thing that’s moving, and nothing irreversible has been, or will be done.
OK that is reassuring, but still a bit annoying if (like me) you have just come back from a month offline with a bunch of changes you'd like to be able to commit to a SF repo branch for testing !
-- 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
-- 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