[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Restructured/cleaned git repo (was Re: ECF non-EPL code moved to github)

Lars Vogel has written a manual about the git workflow in Eclipse. 


On Jul 16, 2010, at 8:10, Pierre Henry Perret <phperret@xxxxxxxxx> wrote:

I have used git plugin for Eclipse - EGit -

I have noticed two ways for sharing a project:

 - Commit
 - Push

I think commit is the 'classic' way and prefered trying Push, so after creating a local repo based on project ,
I try to action Push (popup menu on project->Team) then get the rep wizard dialog, enter the ecf-nonepl uri, get the second page and there... cant get forward cause of two fields: 'Source ref' and 'Destination ref' which wizard block me here.
Dont know why ...


2010/7/15 Markus Alexander Kuppe <ecf-dev_eclipse.org@lemmster.de>
On 06/29/2010 11:30 PM, Markus Alexander Kuppe wrote:

> the non-EPL CVS repo hosted at ecf1.osuosl.org has been retired in favor
> of a git repo at github [0]. This means you will have to use git now
> instead of CVS to access the code. Committers will also have to setup a
> github account and be added to the team at github. Just respond to this
> mail with your user name.
> [0] http://github.com/ECF/ecf-nonepl

FWIW: I went ahead and restructured the new git repo by grouping
corresponding bundles into project folders. This means that the generic
features/, plugins/, tests/, examples/ folders should not be used
anymore, but e.g. all code that belongs to jgroups be stored in the
jgroups/ folder.

Subsequently we might want to move each project folder into its own git
repo so that consumers really get what they need/want and not a bunch of
unrelated bundles too. Also helps free the history from clutter.

ecf-dev mailing list

ecf-dev mailing list