-
Notifications
You must be signed in to change notification settings - Fork 145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support traversal of git folders below the castle root #94
Comments
The tests for this addition need to be very thorough since a bug in the handling of this could screw things up in all kinds of ways. To put it differently: The detection of when a |
Hold on, this is actually really simple.
The questions remaining are:
|
Off the top of my head I think that .git folders for submodules were moved to the parent .git folder in git 1.7.8. I could be wrong though. https://jira.atlassian.com/browse/SRCTREE-837 I will keep searching though. |
It does seem like it is 1.7.8:
The one thing that I see in the release notes though is that it seems that this behavior only applies to submodules added with 1.7.8 or greater. If I read that correctly that means that a repo created with a version less than 1.7.8 while using a version of git 1.7.8 or greater could indeed have the .git directories within the submodules. Am I reading that incorrectly? |
Oh boy, yup I get to the same conclusion. I don't think there's a way to figure out with which version a git submodule was added. As far as I can see the only way to get around this, is to filter out all the submodule EDIT: p.s. good job on finding the version :-) |
Come to think of it, this might actually be related to another feature I have been thinking of and may make things easier. |
Thats a great idea. Do you want that feature to be its own github issue and we'll link from it here? Or should we just implement that tied to this issue? |
I created a new issue for it (#95). It's always better to track individual changes like this, so we can reference them in the future, should there be any problems with the feature or extensions to it. |
I agree that this change is larger than this issue. Thank you for creating issue #95. |
If I understand this correctly, this feature will enable homeshick to track git project folders as well? That sounds great. Personally I have 2 git working dirs in So if the main issue seems git's inability to track git working dirs inside git working dirs, then isn't this a solution? - http://stackoverflow.com/questions/4659549/maintain-git-repo-inside-another-git-repo |
As discussed in #93 it can be very useful at times to fiddle with
.git
repos by using homeshick. To do that homeshick needs to stop skipping files and folders named.git
whenlink
ing.However, some things still need to be skipped:
.git
folder in the root of a castle, since that is a folder managed by git and not the user.git
files in submodules of a repo.git
folders in submodules of a repo for older git versions (if I remember correctly git switched to just managing all submodules in the.git
folder of the root repository, so we need the git version where that changed)The text was updated successfully, but these errors were encountered: