I don't think there is a way, but I've been wondering about that too. It should be "simple enough" but hopefully the github folks have something in the works to easily do that.

On Sep 4, 2008, at 11:45 AM, Sean Cribbs wrote:

Jim,

I'm actually of half a mind to just make radiant's version a fork of ntalbott's. Maybe I'll check into that.

Sean

Jim Gay wrote:
Great! Now just to convince users to fork that repo instead.
Rainer, sorry to hijack your thread. If you find that Nathaniel's repo works for you, send him a note to push changes to the official one... or perhaps he's reading this right now...

On Sep 4, 2008, at 11:37 AM, Sean Cribbs wrote:

Jim,

I gave him access already.

Sean

Jim Gay wrote:
Is it possible then to hand over the keys to the radiant mailer repo to ntalbott?

This network http://github.com/radiant/radiant-mailer-extension/network/members
and this network 
http://github.com/ntalbott/radiant-mailer-extension/network/members
show entirely different users.

I fear that this is a path to endless confusion for new users down the road where the official version has some bug, but unbeknownst to a new user, some other (non-github-forked) repo has fixes and other features.

If most developers are using github, then we should encourage only one tree for a particular repository. If someone wants to fork it and host it on gitorious, well then that's a different story.


On Sep 4, 2008, at 10:37 AM, Sean Cribbs wrote:

Rainer,

I'm not sure. You might try upgrading to a newer version of mailer. Try the one at http://github.com/ntalbott/radiant-mailer-extension

Sean

_______________________________________________
Radiant mailing list
Post:   Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site:   http://lists.radiantcms.org/mailman/listinfo/radiant

Reply via email to