[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Honestly I did not try egit I am basing it on discussion here.
But as long as it support the following scenarios I am good:
Check in
Check out
Update
Synchronize and view diff
Apply patch
Create multiproject eclipse patch
Switch to another branch/tag/revision
Merge from branch/tag/revision in place
History
Annotate
Compare
Revert to base
On Tue, Jun 8, 2010 at 4:21 PM, James Blackburn
<jamesblackburn@xxxxxxxxx> wrote:
> I almost regret mentioning merge now, perhaps it was a bad example as
> merging isn't something CVS supports.
>
> Alena it would be interesting to know how you currently merge in CVS?
> The way I've done this in CVS, when back-porting patches to the stable
> branch, is to use use the history view and manually re-apply the patch
> to the branch.
>
> I last used egit in 0.6 (and had issues with the hisotry view),
> however I bet this is now much better. If these simple workflows work
> then I really don't have an objection.
>
> Perhaps we need a few bugs:
> - Investigate whether working on HEAD and the maintenance branch can
> work using the existing egit tooling.
> Alex as the local egit representative maybe you could fill us in on
> the existing gotchas / pit-falls that might be a barrier?
> - We need to work out the granularity of the git repos. All of
> CDT is hundreds of MB which I thought was a bit big... What do people
> think?
>
> Cheers,
> James
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
