Andy Parkins wrote:
On Thursday 2006 November 30 14:00, Stephan Feder wrote:
Again I do not see the problem. Probably I have a much simpler picture
of submodules: They are just commits in the supermodule's tree.
Everything else follows naturally from how git currently behaves.
How are these commits any different from just having one big repository? If
some of the development of the submodule is contained in the supermodule then
it's not a submodule anymore.
Right now you only have commits of the top directory aka the super
project. Every subdirectory is just that: a directory (which git stores
as trees).
Now, if you have a subdirectory that git stores as a commit, not a tree,
you have a subproject. It is a directory with history, and because the
commit is part of your superprject, you have access to this history.
Why bother with all the effort to make a separation between submodule and
supermodule and then store the submodule commits in the supermodule. That's
not supermodule/submodule git - that's just normal git.
No, it is not. Currently, there is no way to store a commit within the
contents of another commit. You can only store trees and blobs.
Surely the whole point of having submodule's is so that you can take the
submodule away. Let me give you an example. Let's say I have a project that
uses the libxcb library (some random project out in the world that uses git).
I've arranged it something like this:
myproject (git root)
|----- src
|----- doc
`----- libxcb (git root)
This works fine; with one problem. When I make a commit in myproject, there
is no link into the particular snapshot of the libxcb that I used at that
moment. If libxcb moves on, and makes incompatible changes, then when I
checkout an old version of myproject, it won't compile any more because I'll
need to find out which commit of libxcb I used at the time.
OK.
Submodules will solve this problem. In the future I'll be able to check out
any commit of myproject and it will automatically checkout the right commit
from the libxcb repository.
OK, I am still with you so far.
Now let's say I'm working away and find a bug in
libxcb; I fix it, commit it. That change had better be stored in the libxcb
repository, and had better make no reference to the myproject repository. If
it doesn't, I'm going to have to pollute the libxcb upstream repository with
myproject if I want to share those fixes.
Here comes the part where we did not meet before.
Of course you do not make any reference from your subproject to your
superproject. You do exactly what you do in git today when you work with
different branches:
Step 1: You fix a bug in myproject's subdirectory libxcb.
Step 2: You commit to myproject. myproject now contains a new commit
object in path libxcb. (How to do that is up to the UI but at the
repository level the outcome should be obvious). This commit is local to
your repository.
Step 3: You propose your changes to the libxcb upstream (it might not be
a repository you have write access to). I use the following made up
syntax (see man git-rev-parse):
A suffix : followed by a path, _followed by a suffix //::_ names the
_revision_ at the given path in the tree-ish object named by the part
before the colon.
Step 3a: Generate a patch
git diff libxcb//^..libxcb//
Step 3b: Push your changes
git push <libxcb-repository> HEAD:libxcb//:<branch in libxcb-repository>
Step 3c: Let your changes be pulled
"Hello, please pull <myproject-repository> HEAD:libxcb//:<branch in
libxcb-repository>"
Step 4: Pull upstream version (hopefully with your changes, otherwise
you have to merge)
git pull <libxcb-repository> <branch in libxcb-repository>::HEAD:libxcb//
See, it works.
From what I understand you want to do the commit and push steps in one
go. How do you want to record local (to your superproject) changes to
the subproject?
Regards
Stephan
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html