[tahoe-dev] github plan?

Greg Troxel gdt at ir.bbn.com
Sun Mar 3 23:10:36 UTC 2013


David-Sarah Hopwood <david-sarah at jacaranda.org> writes:

> On 03/03/13 16:12, Greg Troxel wrote:
>> 
>> I have a repo cloned from "warner", and so do a lot of others, but now
>> it seems like the tahoe-lafs organization account is the official repo.
>> So I am wondering if I (and everyone else cloned off warner@), and maybe
>> even Brian's repo, should remove them and re-fork off the official one.
>> 
>> https://github.com/warner/tahoe-lafs/network/members
>
> If Brian's repo re-forked, would that would disrupt viewing the history
> before the point at which tahoe-lafs/tahoe-lafs was originally forked
> from it? I don't know.

A good point.  But I think that Brian's master branch matches the one in
tahoe-lafs/tahoe-lafs (once caught up, perhaps very promptly), and that
if one has a master branch that is supposed to match, the history is
actually the same.

> It's not strictly necessary for other repos to re-fork. The advantage
> of doing so is that they'll get updates from trunk faster, because they
> won't have to wait for Brian to pull from trunk to his repo. But not
> re-forking does not create any impediment to integrating patches from
> those repos.

I think that's true.  reforking does mean pull requests go to the right
place.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 194 bytes
Desc: not available
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20130303/b2fda7eb/attachment.asc>


More information about the tahoe-dev mailing list