Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [e4-dev] Git best practices

http://wiki.eclipse.org/Platform-releng/Git_Workflows

This page is very helpful for working with the Eclipse Git repositories.

Perhaps there were additional changes in your workspace when you committed, possibly from doing a reset or switching branches.  You should double check what is in the commit you are trying to patch (History View > Right click > Show in commit viewer).

Curtis


From: Joseph D Carroll Jr <jdsalingerjr@xxxxxxxxx>
To: E4 Project developer mailing list <e4-dev@xxxxxxxxxxx>,
Date: 2012/07/25 08:52 AM
Subject: [e4-dev] Git best practices
Sent by: e4-dev-bounces@xxxxxxxxxxx





After working on my first patch [1], I ran into several difficulties creating a useful patch.  If I just committed and selected the commit from the history view, it would create a patch with my changes but it would also include many other changes.  I am assuming they are the changes from the previous commit as well, and I have triple checked to make sure I selected the right commit.  Also, after committing something I might realize a defect and have to commit the changes, but I will have to revert the previous commit because I am not able to select multiple commits to create a patch.

So I am assuming there are a number of things I am doing wrong.  Does anyone have any "best practices" or advice for a guy just starting with git & e4 development?

Thanks,

JD

ps-  I have the EGit user guide and I reference that as much as possible. [2]


[1] http://bugs.eclipse.org/bugs/show_bug.cgi?id=385414
[2] http://wiki.eclipse.org/EGit/User_Guide

_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/e4-dev



Back to the top