[petsc-dev] petsc-dev on bitbucket

[Barry Smith]

On Feb 9, 2012, at 11:15 PM, Sean Farley wrote:

>    
> Even if you were right about this specific issue (which you are not) it doesn't matter. All you've done is removed the need for a releases subdirectory. What about tutorials subdirectory, externalpackages subdirectory, anothercoolthingwethinkofnextweek subdirectory.
> 
> Why does the *server* have to have the subdirectory?

   Because I want to have a bunch of repositories organized in a hierarchical manner. You response seems to be:

1)   no you don't want that   or

2)  you should put them all in one giant repository   or

3) have them in different bitbucket accounts (like a petsc account and a externalpackages account) that have nothing to do with each other.

   Just admit that not supporting a directory structure at bitbucket is lame and stop coming up with lame reasons why it is ok. Then get bitbucket to add this elementary support and we'll be all set.

   Barry




> 
> $ hg clone bb://petsc/anothercoolthing subdirectory-that-can-suck-eggs/anothercoolthing
>  
> Please explain to me the real reasons bitbucket is better than petsc.cs.  and stop rationalizing around bitbuckets weaknesses. Every choice has some tradeoffs and I haven't heard much about bitbuckets advantages so I am confused why you guys are so in love with it. (Well I understand Sean's reasons, being pretty lazy myself :-)).
> 
> I'll let Jed explain about forks and have the reverse look-up (how many people have forked petsc). For me, it's drop-dead simple management.