https://github.com/perigrin/moose-collection

Moose Git Repositories in git submodules
https://github.com/perigrin/moose-collection

Last synced: 22 days ago
JSON representation

Moose Git Repositories in git submodules

• Host: GitHub
• URL: https://github.com/perigrin/moose-collection
• Owner: perigrin
• Created: 2009-04-17T12:25:04.000Z (over 15 years ago)
• Default Branch: master
• Last Pushed: 2009-04-17T06:15:51.000Z (over 15 years ago)
• Last Synced: 2024-05-01T22:51:36.953Z (8 months ago)
• Homepage:
• Size: 93.8 KB
• Stars: 2
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README

Awesome Lists containing this project

README

        
Moose Collection

~~~~~~~~~~~~~~~~

This project is a git 'superproject' for Free Moose components

available via git.

Until it is known that git's submodule support handles it well,

projects will never be renamed/moved.

In general there will not be a new superproject commit for every

submodule commit; if you want the very latest from each of the

submodules you will have to pull them individually.  However, the

following branches will be defined;

  - stable - representing only CPAN released versions of modules

  - dev - representing CPAN development releases

  - master - collecting 'master'-quality branches from sub-projects

           where available, or latest stable CPAN release where not.

  - next - collection 'next' branches - ie, branches which are heading

           towards being 'dev' releases.

  - pu - collecting 'trunk'-quality branches.

'master', 'next' and 'pu' will be subject to time-based update,

probably on an hourly or thereabouts basis.  'stable' and 'dev' will

be updated as new already added CPAN releases are noticed, or as

conformingly named signed tags in subprojects are noticed.

To make things sane I'll be trying to smoketest branches before

updating them, except 'pu' which will just be whatever the 'latest and

greatest!!1!1' is upstream.

Instructions and helper scripts will follow, but for now you'll have

to spend the few minutes it takes to learn how git submodules work;

note if you don't understand the DESCRIPTION part of a recent

git-submodule(1), I recommend first the git user manual section on

"git concepts".  eg

http://www.kernel.org/pub/software/scm/git/docs/user-manual.html#git-concepts

If you would like your own free Moose project considered for

inclusion, please send through a patch to this superproject which adds

it.  You can send them to the Moose user's list;

    The mailing list is [email protected]. You must be

    subscribed to send a message. To subscribe, send an

    empty message to [email protected]

Enjoy!

Sam Vilain, evil Moose Conspirator, wing commander of sideline sniping

squadron.