Bugzilla – Full Text Bug Listing
| Summary: | please create org.eclipse.m2e.workspace git repository | ||
|---|---|---|---|
| Product: | Community | Reporter: | Igor Fedorenko <igor> |
| Component: | Git | Assignee: | Eclipse Webmaster <webmaster> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | thanh.ha |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Igor Fedorenko
I created your new repo as org.eclipse.m2e.workspace and set the permissions similar to the Gerrit permissions on m2e-core. Let us know if something is not right with the permissions. (In reply to Igor Fedorenko from comment #0) > I am not certain about eclipse git repository naming conventions. If > org.eclipse.m2e.workspace.git is not appropriate, m2e-workspace.git is okay > too. Typically org.eclipse.project.repo.git is the naming convention we give when we create a new repo. I'm not entirely sure why your existing repos don't have that convention though. (In reply to Thanh Ha from comment #1) > I created your new repo as org.eclipse.m2e.workspace and set the permissions > similar to the Gerrit permissions on m2e-core. Let us know if something is > not right with the permissions. > I was able to push my code to the new repository. Thank you, Thanh. > > (In reply to Igor Fedorenko from comment #0) > > I am not certain about eclipse git repository naming conventions. If > > org.eclipse.m2e.workspace.git is not appropriate, m2e-workspace.git is okay > > too. > > Typically org.eclipse.project.repo.git is the naming convention we give when > we create a new repo. I'm not entirely sure why your existing repos don't > have that convention though. This is likely because we were one of the first eclipse projects to use git, before the convention was established. |