Am 2012-10-10 08:02, schrieb Thomas Ferris Nicolaisen:
One repo should have one versioning scheme. Think about tagging. You want to
versions of lua "1.0", "1.1", and so on. If you keep a lot of products in one
repo, it will be filled with tags of different versioning schemes like "lua-1.0,
zlib-5.3" and so on. This works as well, of course, but it doesn't feel "clean".
Separation of concerns and all that.
Well, I use tags not only strictly for versioning, but also for attaching generic labels
That is, in the *vendor* branch, my tags (in the verbose form) simply express something
"From this commit on, we use (or rather 'start using') lua 5.2".
Next commit tag in vendor branch might maybe express:
"From this commit on, we use (or rather 'start using') wxwidgets 2.9.12".
That's all. No tag is expected to give an exhaustive list of the version of
Thanks for your help, I'm currently working on implementing it!
Cafu - the open-source Game and Graphics Engine
for multiplayer, cross-platform, real-time 3D Action
Learn more at http://www.cafu.de
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to
For more options, visit this group at