On Tue, Jun 30, 2009 at 8:24 AM, Ryan Krauss<[email protected]> wrote: > So, I don't feel ready to join the git mailing list and am posting my > question here instead. I know there are knowledgable git people here. > Sorry if this is annoying. > > I want to set up some git projects to better collaborate with my students. > I think it will be cleanest and easiest if there are multiple projects so > that my students are not forced to navigate all my code. My grad students > for example need access to much more code than my undergrads. The overload > would probably scare most of the undergrads. > > So, my main question is this: what do I do with python files that are needed > by everyone? I have some smaller untility modules that are just kind of > misc or common or basic. I don't know if I am ready to learn git-submodules > yet (maybe it isn't that bad). But I don't know what my options are. I > could see creating a misc or common or basic git project, but it will > probably be the case that my other projects won't work unless you check out > the misc project first. Maybe that is fine.
I think the git submodules is a solution to this. I only used that with cgit --- a nice web interface to git, that has git itself as a submodule, so that it compiles. Everything just works. You can of course also just copy the file around in all those git repositories. How many files is it? Do you change them often? Ondrej --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sympy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/sympy?hl=en -~----------~----~----~----~------~----~------~--~---
