in reply to What's in a Repo?

Which of these folders do you want to get in your pull?

You mean checkout don't you :)

How about only the (latest) files that end up in a cpan distribution? Just tag it blead (or bleaddist/bleadcpan).

My role would be to fix a single-glaring-easy-to-fix-bug I encountered, which I would usually submit as a patch against your latest cpan tarball

In all honestly I would never be involved with your module, because magic module is magic :)

Replies are listed 'Best First'.
Re^2: What's in a Repo?
by Xiong (Hermit) on Aug 07, 2010 at 12:09 UTC

    I mean, What contents do you want to see in that repo?

    Most people seem to think 'blead' is an alternate speling of 'bleed'. Googling 'bleaddist' turns up exactly one page: This one. Would you be willing to elaborate? I'm not asking how anything should be tagged.

    Note: Contents may change.
[reply]
[d/l]
      What contents do you want to see in that repo?

      Everything you want to publish , as long as I can always checkout the bare bones cpan distribution branch.

      I think everything should go into your private repository, but you should only share/publish (like on github) that which isn't private. According to your original post everything should go into your public repository except maybe some config files (local passwords/keys)

      blead is blead (trunk in svn parlance, current main branch), something perlhackers will understand, and you might want to explain in some kind of REPO-README

[reply]

In Section Seekers of Perl Wisdom