On Tue, 11 Mar 2008 10:31:06 +0100, martin f krafft <[EMAIL PROTECTED]> said:
> Are you sure? I suggest you read the discussion logged at > http://colabti.org/irclogger/irclogger_log/git?date=2007-09-06,Thu&sel=578#l979 > The important thing to note is that the current commit of a submodule > is a feature of the supermodule. If the submodule's repository gets a > new commit, your submodule clone will *not* be updated until you > explicitly update it. Once you did that, you *also* have to commit a > change to the supermodule. > You may want this just as well, but I feel you need to explicitly > consider it. I have done some experimentation with this, and I can say this is a definite feature. I updated my ./debian/common submodule with what I thought was a backwards compatible update, but it only happened to be backwards compatible for _some_ of my packages. It was nice to still have buildable packages until I make the changes in each package to make them work with the new ./debian/common changes. Just another data point. manoj -- It is not well to be thought of as one who meekly submits to insolence and intimidation. Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/> 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C _______________________________________________ vcs-pkg-discuss mailing list vcs-pkg-discuss@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/vcs-pkg-discuss