On 04/08/17 9:58 , Richard Haselgrove wrote: > Is there also a change in the definition of a 'tag'? In SVN days, a tag > - which we used to identify client code, nothing else - included only:
A git tag is just a label you stick on a given commit. Nothing more, nothing less. How you use them is up to you. If you tag a client version then you just express which state of the (whole) repo was used to build it. That's all. That said, it's (normally) irrelevant for the client build what Drupal-related code was in the repo at build time. However, other components might indeed have an (unknown side-) effect on the client build so it's actually a huge advantage to know the state of the whole repo at the time of the build. There are a lot of "Git for SVN users" tutorials out there. Just have a look if you're curious. We migrated from SVN to git not just for the hype, but because of its blatant advantages for what we do. Sadly BOINC is still barely making use of it. HTH, Oliver
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
