Eclipse: How to create patch for branches?

Moving to the docs queue

Read this carefully: https://docs.google.com/document/d/1plu1PjGjMTpQzmX18Vd4PY17lDGELxg_kCJQ...

Short version:

1) go to a branch
2) make changes
3) commit those changes (yes you need to commit stuff)
4) right click ==> team ==> show in history
5) right click the commit on top ==> create patch

And no you can't patch (yet) files between random commits in egit

Hass, you commit *locally*, you have a full copy of the history on your *local* computer, that is how git works...
Your commits wont be pushed to the server and you can commit as much as you can even if you don't have any permissions.
Only when you push your *local* commits to the server you need permissions.

Read the git handbook (http://drupal.org/documentation/git) if you would like to know more about git.
Git is not something that is rdy for production its a general version control system that is used by many people an systems. (look at github).

If you got troubles with applying patches, just read the manuals I wrote and that are available on the net.

We shouldn't rollback as CVS is crap.

There were a lot of troubles with CVS. File renaming is just one of those.

To answer on your git problems
==> Yes these are egit issues, complain in the egit issue queue. They are still in alpha.
==> If you hate egit learn command line tools
==> If you hate command line tools you hate me lol

To wrap this up: YOU HATE EGIT. If I could I would moved this to the egit issue queue.
And all the docs are made by people like me who put lots of efforts in making the transition as easy as possible.
I'm a total git noob and I after a few weeks I loved it. You just need to get a grip on the tools. And read a lot of docs and books.
Every programmer should evolve and not stick to any crappy tools they know from their past. And it's not because you didn't have any problems with CVS that others have no problems. They maybe need some more advanced functionallity you never needed.

And seriously I'm not a hard person but if you got such a little respect for everyone on here (yes I take this a little personal). Than I don't know if I'm ever going to help you again while you're asking for support.

tags

hass: if you have having problems with EGIT and eclipse, then be sure to search out documentation on eclipse and EGIT and ssh.
You *can* use ssh to connect with eclipse and egit. Here are some rough steps and notes:

Note: git.drupal.org uses a rsa SSH key

1. Be sure you have a valid public/private SSH2 key pair on your local system.
2. You need to give Drupal.org your public key. Log in to drupal.org, go to your profile page, and on the SSH tab, add your public key. (You may need to apply for SSH; search d.o for docs on that.)
3. Let eclipse know about your SSH2 key(s):
   1. (in eclipse) go to Preferences > Network Connections > SSH2 You should see tabs there that let you manage your local SSH2 keys (as well as generate them.).
   2. on the 'Authentication Methods' tab (Preferences > Network Connections > SSH2 : Authentication Methods), move "publickey" to the top of the list and be sure it is selected. You can select whatever other authentication methods needed here as well.

   Now eclipse should be able to user your SSH2 key when you log in to systems, git.drupal or otherwise.

4. These are the settings for a Drupal (source) Git repository. (Used to connect to a Drupal git repository using SSH2 with EGit to either clone to a repository or connect to a remote one; when you import a Git project or whatever your process/workflow)
   
   (As you fill in the information, EGit will automatically build the URI. Or you can just type in the full URI if you know what it is.)
   1. host: git.drupal.org
   2. repository path: /project/[the name of the drupal project you're getting the repo for].git (ex: /project/views.git)
   3. Connection protocol: ssh (you can leave port blank / accept the default)
   4. Authentication User: [your drupal.org id]
   5. Authentication Password: leave this blank; eclipse should then try to use your SSH2 key if you've set that as the first Authentication Method in the steps above (or if it's at least higher in the list than 'password')

- - -
hass, I share your frustration about the spotty documentation on the EGit tools. Documentation in the software world varies all over the place; documentation for open source projects tend to really be spotty and often lacking IMHO. But also realize that major companies have been using eclipse since it was developed in the 90s. And Git is used by major corporations as well. So someone out there is making it work; you have to try to track them down and get the info.

This response comes quite a while after your initial post (I wasn't using EGit then), but perhaps it will still be helpful to you, and perhaps it can serve as a draft for a documentation page so it will help others.

Of course you can create a patch with eGit. You can even use 'right click' to do it. I did it a number of times this weekend.
In the Git perspective, with the history list for a branch, I can right click and choose 'create patch' then choose to create the patch in git form (my preference). I saved the resulting patch with an appropriate file name. That was it.

All of your issues seem to be with the eGit tool. They aren't about git. Folks have tried to help you out by taking the time to write up steps for you to follow. If they aren't providing you with the information you need then you need to be clearer about what it is you want.

If what you want is for eGit to be a better tool with better documentation, then you need to go over to the eGit project on eclipse.org and work with the folks there. All we can do here is to try to work together to document how to work with that tool; we cannot change that tool. If eGit is causing you so much pain, then explore other tools out there. If your workplace forces you to only work with eclipse and eclipse tools, then you need to discuss that issue with the powers that be in your workplace. None of us can do anything about those issues for you here with the documentation project on drupal.org.

So hass: If this is an issue of documentation for the drupal.org site, what, exactly, is it that you would like to see documented? If you could provide a rough outline of what it is you want to accomplish, then perhaps that would be clearer, and then others could begin to fill those steps in.

In #10 you state that you need to be able to create a patch with eGit, and that you want to be able to use right click to do so. You also state that it's "no longer possible to share a patch the easy way like in the past." Please tell us what the steps were that were "the easy way like in the past" so that someone can possibly let you know how to accomplish it currently and then you can write up the documentation so that everyone can benefit.

And just because something isn't "the easy way like in the past" for you doesn't make it a critical issue. You can review information about issue priority in http://drupal.org/node/73179 and http://drupal.org/node/45111. This issue is obviously *not* stopping people from contributing patches successfully to drupal.org.

1) Stop being a freaking idiot...

2)
==> READ <== http://drupal.org/node/1077484 and follow the steps.
And yes here are two screenshots if you can't read.

Btw did I say you actually have to read and try those steps? It's a wiki you know that? If you find a failing step you can actually *change* the step so others can learn from it. It's MAGIC...
And when you're trying those steps you can even make some screenshots! AWESOME
And as an extra you can share those screenshots with the world!

It requires a click +/- 3 clicks to create a patch. 10 if you order a book on amazon before creating the patch...

3)
Reset a branch? What about googling: "egit reset branch"
Maybe... If you're one of those lucky people... it will link you to: http://wiki.eclipse.org/EGit/User_Guide#Reset_to_specific_branch_or_tag

4)
"Aside of this I heard that everyone who creates a patch will invalidate other patches. "
I heard that drupal Dries landed on mars with his 3 tiny horses...

5)
My grandmother uses IE6 because she thinks its plain *easy*, she thinks firefox or google chrome is horrible. That doesn't mean she is right...

Critical support request?

This thread has gotten abusive and does not belong on drupal.org or in the Documentation issue queue. I am closing it.