forks and pull requests are probably the easiest for everyone involved Jeremy
On Wed, Sep 3, 2008 at 7:30 AM, Jay Levitt <[EMAIL PROTECTED]> wrote: > Chris Hapgood wrote: > >> I too have added a >> >> git submodule init;git submodule update >> >> to my build scripts >> > > I was thinking of having my rake task run that only if the plugin dirs are > empty. This solves the initial problem of a fresh git clone. It doesn't > solve later problems when new submodules are added - but neither does it > UNsolve the "I cloned against HEAD of acts_as_plugin, and the developer just > changed things" problem that svn:externals has, and that submodules solves > so nicely. > > > -but I'm not calling a rake task directly and I'm > >> using the git-enabled branch of CC.rb from Ben Burkert instead of the >> Thoughtworks one. >> > > And I should clarify that I am, in fact, using the Thoughtworks > branch/tree/whatever from github. > > Which reminds me - Thoughtworks, do you prefer patches as patches, forks > and pull requests, no idea yet? I've noticed a few minor things that need > polish, and I also want to get this working well in a non-rooted URL, since > I use it over HTTPS, and NameVirtualHosts on HTTPS are a nightmare, even > with wildcard certs. > > Seems like git submodules need some love in both cases. I would hope that >> the submodules would be init/updated as part of the scm updating process... >> > > I've seen some talk around the web of piston being updated for git, and of > a new thing called braid, but neither seem to be soup yet. > > Jay > > _______________________________________________ > Cruisecontrolrb-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >
_______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
