I would suggest forking on github, pushing up your changes to your fork,
and then creating the submodule from the fork. If you don't want to
track other branches/forks but just keep your changes in the Radiant
project, just clone the extension (not as a submodule) and then remove
its .git directory.
Sean
Nate Turnage wrote:
On Wed, Dec 31, 2008 at 7:25 AM, Sean Cribbs <[email protected]> wrote:
One thing I forgot to mention. Whenever you clone the project again, you
need to run:
$ git submodule init && git submodule update
This will make sure you download the submodules.
Thanks for your help Sean. Now I have another related question. I am using
the subscriber_lists extension but on my copy I changed a couple of things.
Since I cannot use submodule to include the extension, how can I tell git
ignore the fact that it was a cloned copy of the one on github? Or, barring
that, how can I download a copy of the code from github (think svn export)
to make the changes and track the code in my own repo?
Thanks,
Nate
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
_______________________________________________
Radiant mailing list
Post: [email protected]
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
