title: Developing a Git library project that's also a submodule of another project
body: <p>I have an Android application under development which makes use of a separate library project of my own. These two projects are stored in separate Git repositories. The application project references the library project by means of the <code>.gitmodules</code> file. </p>
  
  <p>I'm now trying to work on both of these projects together (the application and the library) on a new machine. I cloned the application project, which resulted also in the library project being automatically cloned into my ~/git/ directory as well. So far so good. </p>
  
  <p>I notice also that in Eclipse Package Explorer, the library project root has a commit hash within brackets (e.g. <code>[MyLibraryName 0123ABC]</code>). This presumably means that the library clone is from a certain commit point, and I understand that I could update this (i.e pull in the latest commits for this library) using <code>git submodule foreach git pull</code>. </p>
  
  <p>Question is, what is the best way for me to continue separately developing the library project now? I tried to modify a file and stage it, but when using Team->commit, the dialogue didn't list the modified file. I assume this might be something to do with it being a submodule, pointing at a particular commit. </p>
  
  <p>Should I clone my library project again, completely separately into a different subdirectory, and import as a separate project into Eclipse in order for me to do work on that library?</p>