Hello, guest. We have noticed that you are not registered at this bug tracker. Your experience will be greatly enhanced if you log in. To do so, you first must register by clicking on the Register tab at the top. If you are already registered, you can login at the Login tab.
Syndicate Syndicate Listing New Display Search Login/Register
Bug Id ?
Reporter ?
dherring
Product/Version ?
LibCL Distribution / 0.1
Status ?
Confirmed
Severity ?
Moderate
Duplicate Of ?
- none -
Summary ?
libcl doesn't tag the git repos
Report Time ?
December 21, 2008 09:00:01 PM
Assignment ?
dherring
Resolution ?
Open
Priority ?
Normal
Dependencies ?
- none -


Votes
For: 0 (0%)
Against: 0 (0%)
Total: 0

December 21, 2008 09:00:01 PM dherring
This doesn't affect snapshots, alphas, or betas (where the collection of SHA1 ids is sufficient); but release builds of libcl should tag all git repos with their directory name.
These tags will ensure that the proper git tree is always available (fetch/push --tags), especially in the case of branch switches.

Alternatively, it probably makes more sense to have a parent project which used submodules to track the libcl sources and upstream libraries...