| Summary: | Git migration request | ||
|---|---|---|---|
| Product: | Community | Reporter: | Eric Gwin <eric.gwin> |
| Component: | Git | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | douglas.clarke, peter.krogh, tom.ware |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Eric Gwin
+1 to most, but if possible I would like the examples kept a litte longer than a month. We have wiki sites etc that point to the svn locations of the examples, and we will need to point those to the current repo before removing. Based on a suggestion from Eric I'm trying to use git filter-branch to extract these from the huge initial import. If that doesn't work out the only other thing I can think of is dumping the SVN, filtering the dump and then creating a new temporary SVN repo to use for the git conversion. -M There were some checkins to examples since December. If you're already in progress, I think we could also 'recreate' the couple of transactions. If not, you could remove the old o.e.eclipselink.test.git and reimport before your filter-branch. I believe I was the only one using it - and I can stay away, if that's what you need. Also, FYI. The link to doing the git filter-branch I was using can be found here: http://stackoverflow.com/questions/359424/detach-subdirectory-into-separate-git-repository I'm not certain how well it would work because I ran out of memory re-packing the new repository. This stalled due to limitations with the migration tool. In addition, doug decided that history was not very useful for the examples, and so he asked for an empty repository to be created. This has been done and matt made the following repository available last week: git.eclipse.org/gitroot/eclipselink/examples.git Doug has since pushed one example to the repository using Indigo/Egit (Last thursday?). I was able then able to clone the repository myself. His second attempt to push is resulting in a "refused" message. Since the commit was successful to his local repository, it appears to be a permissions issue. Is there anything we need to do so that access is assured? SSH keys, etc? While using a key will prevent having to enter your password, I don't think that authentication is the issue Doug is seeing. I was able to commit a simple change(via git on linux) to the examples repo acting as Doug, so I suspect there is something in the Git plugin that's failing with this rather cryptic error. -M. I'll assume all is well here. Please reopen if not. |