[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] Layout when the project is in the repository root
|
On Dec 17, 2009, at 16:38, Gunnar Wagenknecht wrote:
Am 17.12.2009 16:04, schrieb Shawn O. Pearce:
And they would be in the same branch together as you would checkout
the higher level trunk folder.
And here in lies an issue. AFAIK the Eclipse Team Integration workflow
was designed/optimized for checking out projects into the workspace.
It defaults to that, but I'm not sure it was optimised to do so in any
way. After all, it's just a folder.
There's two (distinct) use cases here, I think;
1) Users who already have Git projects checked out on disk (e.g. via
headless build systems, command lines etc.)
2) Users who are driving Eclipse to do all their work
The former would be quite happy with having multiple projects in the
same repository, and indeed, may experience problems if doing
something else.
The latter; if you start putting the repository somewhere else
automatically, then I'm sure things will go wrong (especially if it's
in the .metatdata - a common user action is 'delete the .metadata and
rebuild' when problems are experienced). It would be better to allow
the user, when checking out a project, to be able to nominate where
the root of the project lives. Thus in the branch-and-patch scenario
you outlined, you'd have two git repositories, one branched at HEAD
and the other branched at RELEASE_3_5_1 or whatever. Projects could
then be pick'n'mixed between the two.
Therefore, it might make sense if EGit were able to easily do a
'migrate' between one on-disk repository and another of a project to
facilitate switching between branches, since branch is a repository-
wide concept and not a project-wide concept. It might even make sense
to permit, during the branch operation, to clone a repository to
somewhere else just to facilitate single project branching.
Alex
