On Wednesday, August 10, 2016 at 12:37:46 AM UTC+3, Marek Marczykowski-Górecki wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > On Tue, Aug 09, 2016 at 02:23:02PM -0700, [email protected] <javascript:> > wrote: > > Now that I look more carefully the submodule configuration, all the > > submodules seem to refer to certain snapshots of 3.1 release versions. > For > > example reference to version of gui-common is also almost 1 year old. > > Even by modifying .gitmodules and adding "branch = xen-4.7" to > > core-vchan-xen the reference stays the same and manual > > intervention/checkout is needed. And if the snapshot reference is > updated, > > then this has to be redone every time a new patch is applied to the > target > > submodule repository. I'm not familiar at all with these advanged git > > options, so what's the best way to keep track of changes in submodules? > > By design submodule points at exact commit id, so in any case manual > intervention (commit) is needed. And this is actually a feature - commit > id of parent repository determine state of the whole source tree. This > makes for example tags meaningful even when submodules are used. > > So the thing here is to remember (or have some external reminder) to > update submodule when needed. And in fact this "when needed" isn't > necessary each time the commit is made there. > > In case of gui-common, it probably doesn't matter for now - gui agent in > stubdomain (this is why gui-common is linked there) support only very > some subset of the protocol and doesn't care about new messages. The > protocol is especially designed to allow such compatibility - gui-daemon > must be newest available, but gui-agent can be older. > > But vchan submodule needs to be updated for xen 4.7, of course. > > Ok, that makes sense. Thanks for the explanation.
The vchan-xen reference is now updated on my repo. - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJXqk0kAAoJENuP0xzK19csCvwIAIaM+mrWiDVxnyene0VPQ4oS > wcqxQBqo6HDLtscVQqIY9GPN9TOVepn/CUxsIiRvZT8/l54jchY8lFw7EzBVbpwf > ghyETSljn9TPZVBxtSmWGEl8+NaIXyTDEwj8HG81ZU+K0eKgYvMzuPnzeJmUyAww > XBHKS5FZFxmr6WAsfwLW0krt5DFJarRoRs44bTCmhgukgCU0u/QJephm37uNztn8 > fZL7u7iJNGHRgJgDpZ4cIXlopHgNTpl+jUNTTd8ZR8eLniF885dsOhg3eMRGw6R6 > SIjp7xmrFUShUHpsfXseuXNdTJBwZo0CRuuDzMWtw+DRbZ7LWsNq2Zx8NQMp2Ec= > =xBQN > -----END PGP SIGNATURE----- > Best regards, Marcus -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-devel/5cdced0e-21a1-4842-9e20-98dacc72ff76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
