[petsc-dev] petsc-dev on bitbucket

I just pushed to bitbucket and my write permissions were revoked. 2012/2/27 Jed Brown > On Mon, Feb 27, 2012 at 15:48, Satish Balay wrote: > >> Jed, >> >> Perhaps this is a test case for 'pull request' model? [via petsc.cs] >> > > Sure, Stefano (or anyone) can fork on bitbucket, hack away, th

[petsc-dev] petsc-dev on bitbucket

Hi, I need to push some changes to bddc code. Here is my bitbucket name: stefano_zampini Thanks, Stefano 2012/2/8 Sean Farley > "Yoo, i've switched petsc-dev over to bitbucket since petsc.cs.itt.edu is > down pull/push from https://bitbucket.org/petsc/petsc-dev > > Sean" - Barry impersona

[petsc-dev] petsc-dev on bitbucket

On Mon, Feb 27, 2012 at 16:07, Stefano Zampini wrote: > > I just pushed to bitbucket and my write permissions were revoked. Nobody is pushing directly to bitbucket. We all push to petsc.cs.iit.eduand it gets mirrored to bitbucket. Your old credentials should still work there. -- next

[petsc-dev] petsc-dev on bitbucket

On Mon, Feb 27, 2012 at 15:48, Satish Balay wrote: > Jed, > > Perhaps this is a test case for 'pull request' model? [via petsc.cs] > Sure, Stefano (or anyone) can fork on bitbucket, hack away, then send a pull request. We can merge locally and push to petsc-dev (which will be mirrored to bitbuc

[petsc-dev] petsc-dev on bitbucket

Stefano, We haven't moved to bitbucket yet. [it was a temprary host until the primary server could come back up. We've since then checked if we could migrate permanantly - but hit some snags]. Jed, Perhaps this is a test case for 'pull request' model? [via petsc.cs] Satish On Mon, 27 Feb 2012

[petsc-dev] petsc-dev on bitbucket

> > to get this public=yellow, draft=green, secret=red (image attached) > Forgot to attach image -- next part -- An HTML attachment was scrubbed... URL: -- next part --

[petsc-dev] petsc-dev on bitbucket

> > On the related note - I believe one of the new hg releases has some > improved > support for rebase - so its now safer [provided the right version is used]. > i.e if the change was aready pushed - it warns not to rebase. I haven't > tried this feature though.. It's version 2.1 and the feature

[petsc-dev] petsc-dev on bitbucket

On Fri, 10 Feb 2012, Jed Brown wrote: > On Fri, Feb 10, 2012 at 11:30, Barry Smith wrote: > > > On Feb 10, 2012, at 11:26 AM, Jed Brown wrote: > > > > > One other point is integrated issue tracking. If someone makes a feature > > request, we currently manage it purely by not losing the email. Wi

[petsc-dev] petsc-dev on bitbucket

On Fri, Feb 10, 2012 at 11:30, Barry Smith wrote: > On Feb 10, 2012, at 11:26 AM, Jed Brown wrote: > > > One other point is integrated issue tracking. If someone makes a feature > request, we currently manage it purely by not losing the email. With > bitbucket issues, users can "follow" issues so

[petsc-dev] petsc-dev on bitbucket

On Feb 10, 2012, at 11:26 AM, Jed Brown wrote: > One other point is integrated issue tracking. If someone makes a feature > request, we currently manage it purely by not losing the email. With > bitbucket issues, users can "follow" issues so when we include "closes #123" > (and other status up

[petsc-dev] petsc-dev on bitbucket

One other point is integrated issue tracking. If someone makes a feature request, we currently manage it purely by not losing the email. With bitbucket issues, users can "follow" issues so when we include "closes #123" (and other status updates) in a commit message, interested users get notified. I

[petsc-dev] petsc-dev on bitbucket

On Fri, Feb 10, 2012 at 10:08 AM, Satish Balay wrote: > On Fri, 10 Feb 2012, Matthew Knepley wrote: > > > > until we move to bitbucket - can you continue to push to petsc.cs.iit > > > - and not bitbucket? [for now - pushes to petsc.cs.iit are > > > automatically pushed to bitbucket] > > > > > > >

[petsc-dev] petsc-dev on bitbucket

On Feb 10, 2012, at 9:34 AM, Jed Brown wrote: > On Fri, Feb 10, 2012 at 09:30, Matthew Knepley wrote: > I decent way of hierarchically organizing our repositories. Tell me how to > do this on bitbucket and you have your slam dunk. > > Mailing BB. > > https://bitbucket.org/site/master/issue

[petsc-dev] petsc-dev on bitbucket

On Fri, 10 Feb 2012, Matthew Knepley wrote: > > until we move to bitbucket - can you continue to push to petsc.cs.iit > > - and not bitbucket? [for now - pushes to petsc.cs.iit are > > automatically pushed to bitbucket] > > > > I thought we were switched already :) I cannot understand why we woul

[petsc-dev] petsc-dev on bitbucket

On Fri, Feb 10, 2012 at 9:46 AM, Satish Balay wrote: > Matt, > > until we move to bitbucket - can you continue to push to petsc.cs.iit > - and not bitbucket? [for now - pushes to petsc.cs.iit are > automatically pushed to bitbucket] > I thought we were switched already :) I cannot understand why

[petsc-dev] petsc-dev on bitbucket

Matt, until we move to bitbucket - can you continue to push to petsc.cs.iit - and not bitbucket? [for now - pushes to petsc.cs.iit are automatically pushed to bitbucket] thanks, Satish asterix:/home/balay/spetsc>hg in running ssh petsc at petsc.cs.iit.edu 'hg -R /hg/petsc/petsc

[petsc-dev] petsc-dev on bitbucket

On Fri, Feb 10, 2012 at 9:35 AM, Satish Balay wrote: > On Fri, 10 Feb 2012, Barry Smith wrote: > > > > > On Feb 10, 2012, at 9:13 AM, Matthew Knepley wrote: > > > > > The thread has become too deep for me to read, hence the top posting. > > > > > > Barry's question is the right one: What do we ga

[petsc-dev] petsc-dev on bitbucket

> > As I understand it - for more than 5 folks to be able to access a > private repo - one needs to be on a paid plan with bitbucket. [not a > big deal - but want to put that up front] > Not for educational accounts. Any email that has an .edu is automatically put in that plan. -- next

[petsc-dev] petsc-dev on bitbucket

On Fri, 10 Feb 2012, Barry Smith wrote: > > On Feb 10, 2012, at 9:13 AM, Matthew Knepley wrote: > > > The thread has become too deep for me to read, hence the top posting. > > > > Barry's question is the right one: What do we gain by changing? > > > > 1) Reliability and Availability > > > >

[petsc-dev] petsc-dev on bitbucket

On Fri, Feb 10, 2012 at 09:30, Matthew Knepley wrote: > I decent way of hierarchically organizing our repositories. Tell me how >> to do this on bitbucket and you have your slam dunk. > > > Mailing BB. > https://bitbucket.org/site/master/issue/2323/create-folders-to-organize-the-repository ---

[petsc-dev] petsc-dev on bitbucket

On Fri, Feb 10, 2012 at 9:23 AM, Barry Smith wrote: > > On Feb 10, 2012, at 9:13 AM, Matthew Knepley wrote: > > > The thread has become too deep for me to read, hence the top posting. > > > > Barry's question is the right one: What do we gain by changing? > > > > 1) Reliability and Availability

[petsc-dev] petsc-dev on bitbucket

On Feb 10, 2012, at 9:13 AM, Matthew Knepley wrote: > The thread has become too deep for me to read, hence the top posting. > > Barry's question is the right one: What do we gain by changing? > > 1) Reliability and Availability > >Barry, you should know that this crap about petsc.cs bein

[petsc-dev] petsc-dev on bitbucket

On Fri, 10 Feb 2012, Satish Balay wrote: > > With Bitbucket, GitHub, and all the others, the web account is *not* a unix > > account. It's just a way to manage identity/keys. Everyone using ssh has > > hg at bitbucket.org (and git at github.com, etc). > > sure the implemtation details are differe

[petsc-dev] petsc-dev on bitbucket

The thread has become too deep for me to read, hence the top posting. Barry's question is the right one: What do we gain by changing? 1) Reliability and Availability Barry, you should know that this crap about petsc.cs being backed up is farcical. We would have the same situation we had

[petsc-dev] petsc-dev on bitbucket

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, anothercoolth

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Sean Farley wrote: > > > > Now we are back to the original model of user account - and access via > > this account [yes - bitbucket makes it easier to crate accounts, and > > hopefully better infrastrucutre than 'group permission' for sharing > > underneath. [well atleat there

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Jed Brown wrote: > On Thu, Feb 9, 2012 at 23:50, Satish Balay wrote: > > > On Thu, 9 Feb 2012, Jed Brown wrote: > > > > > On Thu, Feb 9, 2012 at 23:36, Satish Balay wrote: > > > > > > > > > Credential management is simpler because adding/removing keys and > > > > similar > >

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 23:50, Satish Balay wrote: > On Thu, 9 Feb 2012, Jed Brown wrote: > > > On Thu, Feb 9, 2012 at 23:36, Satish Balay wrote: > > > > > > > Credential management is simpler because adding/removing keys and > > > similar > > > > > can be done by the user instead of by emailing

[petsc-dev] petsc-dev on bitbucket

> > Now we are back to the original model of user account - and access via > this account [yes - bitbucket makes it easier to crate accounts, and > hopefully better infrastrucutre than 'group permission' for sharing > underneath. [well atleat there is a gui to it]. Eh, if you really want to, just

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Jed Brown wrote: > On Thu, Feb 9, 2012 at 23:36, Satish Balay wrote: > > > > > Credential management is simpler because adding/removing keys and > > similar > > > > can be done by the user instead of by emailing Satish. > > > > > > replaced by 'crate a bitbucket account - an

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 23:36, Satish Balay wrote: > > > Credential management is simpler because adding/removing keys and > similar > > > can be done by the user instead of by emailing Satish. > > > > replaced by 'crate a bitbucket account - and email sean your bitbucket > id' > > > > so eqivale

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 23:32, Satish Balay wrote: > > hg clone -u release-3.2 https://bitbucket.org/petsc/petsc-release > > hm - don't you miss all the patch commits from release date to the release > tip? > -u can also follow a branch or bookmark too -- next part -- An H

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Satish Balay wrote: > > Credential management is simpler because adding/removing keys and similar > > can be done by the user instead of by emailing Satish. > > replaced by 'crate a bitbucket account - and email sean your bitbucket id' > > so eqivalent. ok - I see your poin

[petsc-dev] petsc-dev on bitbucket

> > replaced by 'crate a bitbucket account - and email sean your bitbucket id' > > so eqivalent. Or create a fork and send a pull request (which any petsc-dev person could accept), so the responsibility doesn't have a single point of failure. -- next part -- An HTML attac

[petsc-dev] petsc-dev on bitbucket

> > 2) Because any idiot who simply wants petsc-3.0.0 (because they are > > using Joe's code which they are not allowed to update) can simply see the > > list of files and grab the one they want. They need to know nothing about > > nothing to do this. Not everyone in the world is an expert Mecuri

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 23:01, Barry Smith wrote: > 1) They are not actually subsets since eventually patches in a release > cannot be applied to the dev so the next release does not have everything > that went into a previous release > If you merge back to petsc-dev right away after committing t

[petsc-dev] petsc-dev on bitbucket

> >hg clone blahblah/dft/log mydft-log or dft/log if they keep a > bunch of them in the dft directory. > If you're using this as your argument, then why not the reverse? Why even look at the website *ever*? $ hg clone bitbucket/petsc/dft-log dft/log 1) They are not actually subsets sin

[petsc-dev] petsc-dev on bitbucket

On Feb 9, 2012, at 10:37 PM, Jed Brown wrote: > On Thu, Feb 9, 2012 at 22:19, Barry Smith wrote: > dft Density Functional Theory solver for Ion Channels petsc-maint > at mcs.anl.gov Thu, 28 Jul 2011 15:05:00 -0600 gz RSS Atom > dft-fft unknown unknown Sat, 19 Dec 2009 13:49:50 -0

[petsc-dev] petsc-dev on bitbucket

On Feb 9, 2012, at 10:54 PM, Sean Farley wrote: > Come on guys, it is completely moronic that bitbucket doesn't support > subdirectories to hold repositories. No amount of rationalization can provide > a reason for this absurdity. > > What's completely moronic is that petsc.cs.itt is hosting s

[petsc-dev] petsc-dev on bitbucket

> > Come on guys, it is completely moronic that bitbucket doesn't support > subdirectories to hold repositories. No amount of rationalization can > provide a reason for this absurdity. > What's completely moronic is that petsc.cs.itt is hosting so many repositories that are mostly cruft: Allen-Ca

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 22:19, Barry Smith wrote: > dft Density Functional Theory solver for Ion Channels > petsc-maint at mcs.anl.gov Thu, 28 Jul 2011 15:05:00 -0600 gz RSS Atom > dft-fft unknown unknown Sat, 19 Dec 2009 13:49:50 -0600 RSS Atom > dft-log Density Functional Theory

[petsc-dev] petsc-dev on bitbucket

I know what we'll do. We'll imbed the directory name and the subdirectory name into the name of the repository: externalpackages_Chaco-2.2 tutorials_ACTS07 Wait a minute, someone who doesn't know about directories already did that: dft Density Functional Theory solver for Ion Channels

[petsc-dev] petsc-dev on bitbucket

> > I think separate clone for release and dev is easy for people to work > with. I think separate clones for every release is clutter. > I agree and think that this would be ideal. -- next part -- An HTML attachment was scrubbed... URL:

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 21:54, Satish Balay wrote: > I interpreted sean as suggesting using 'hg tags' to organize relase patches > and dev changes in a single repo. > Release and dev in the same clone does not work (and was not suggested) unless bookmarks are used. Since that isn't familiar to a

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Matthew Knepley wrote: > On Thu, Feb 9, 2012 at 8:59 PM, Satish Balay wrote: > > > On Thu, 9 Feb 2012, Sean Farley wrote: > > > > > > > > > > Hg named branches are kind of screwy and bookmarks (which are less > > screwy) > > > > are still an "extension" > > > > > > > > > > Th

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Matthew Knepley wrote: > On Thu, Feb 9, 2012 at 8:26 PM, Satish Balay wrote: > > > On Wed, 8 Feb 2012, Sean Farley wrote: > > > > > > > > > > Hell, if you *really* want to, just create the account: > > petsc-release(s) > > > > then the URL would be > > > > > > > > http://bitb

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Jed Brown wrote: > On Thu, Feb 9, 2012 at 20:59, Satish Balay wrote: > > > If we have to create multiple accounts to better organize repos - so > > be it.. > > > > I take it the concern is that we end up with a long list of release > repositories that would look like clutter

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 21:39, Matthew Knepley wrote: > This organization is semantic, and Completely outside the version control > structure. I want something to tell me "this repo is about simulating > rockets" > like Kit, the voice in Michael's car. Tags are fine for this. So is a > hierarchy.

[petsc-dev] petsc-dev on bitbucket

> > I want something to tell me "this repo is about simulating rockets" > like Kit, the voice in Michael's car. > Matt, I wasn't alive at the beginning of Knight Rider and even I know it's KITT for Knight Industries Two-Thousand. -- next part -- An HTML attachment was scrub

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 8:59 PM, Satish Balay wrote: > On Thu, 9 Feb 2012, Sean Farley wrote: > > > > > > > Hg named branches are kind of screwy and bookmarks (which are less > screwy) > > > are still an "extension" > > > > > > > This is true. Named branches are directly inherited from older versi

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 8:26 PM, Satish Balay wrote: > On Wed, 8 Feb 2012, Sean Farley wrote: > > > > > > > Hell, if you *really* want to, just create the account: > petsc-release(s) > > > then the URL would be > > > > > > http://bitbucket.org/petsc-release/petsc-3.1 > > > > > > > Actually, it's e

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 20:59, Satish Balay wrote: > If we have to create multiple accounts to better organize repos - so > be it.. > I take it the concern is that we end up with a long list of release repositories that would look like clutter (although they'll be sorted so they wouldn't be near

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Jed Brown wrote: > On Wed, Feb 8, 2012 at 11:31, Barry Smith wrote: > > > Yes. If you can't have that then it is a pretty crappy system. Sort of > > like IBM 360 where you only had a root directory with a truckload of files > > in it. In excusable in 2012 (or even 1972). >

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Sean Farley wrote: > > > > Hg named branches are kind of screwy and bookmarks (which are less screwy) > > are still an "extension" > > > > This is true. Named branches are directly inherited from older versioning > systems (cvs, svn, etc.). After 2.0 Matt Mackall was convinced

[petsc-dev] petsc-dev on bitbucket

> > IDENTIFICATION DIVISION. > PROGRAM-ID. YOUR-FATHERS-COBOL. > PROCEDURE DIVISION. > DISPLAY 'I do'. > STOP RUN. > And now my eyes are bleeding. Thanks. -- next part -- An HTML attachment was scrubbed... URL:

[petsc-dev] petsc-dev on bitbucket

> > Hg named branches are kind of screwy and bookmarks (which are less screwy) > are still an "extension" > This is true. Named branches are directly inherited from older versioning systems (cvs, svn, etc.). After 2.0 Matt Mackall was convinced that bookmarks so be completely analgous to git's bra

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 20:37, Sean Farley wrote: > Yes, but they aren't guaranteed. Lowercase is the least-common denominator > (plus who programs using capital letters?). IDENTIFICATION DIVISION. PROGRAM-ID. YOUR-FATHERS-COBOL. PROCEDURE DIVISION. DISPLAY 'I do'.

[petsc-dev] petsc-dev on bitbucket

> > hmm - the url 'http://petsc.cs.iit.edu/petsc/buildsystem' doesn't work - > so > atleast apache uses case sensitive urls. Yes, but they aren't guaranteed. Lowercase is the least-common denominator (plus who programs using capital letters?). -- next part -- An HTML attac

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 20:26, Satish Balay wrote: > tags are no good. we implrement branches in different clones. > > You could argue that we should throw away branches in clones have all > clones in a single branch - and change our workflow. > > But I think this will be too confusing to most of

[petsc-dev] petsc-dev on bitbucket

On Thu, 9 Feb 2012, Sean Farley wrote: > > > > Isn't Matt pissed off with this? 'BuildSystem' -> 'buildsystem' > >> > >> [I thought the naming scheme with caps was important - and looks like > >> bitbucket doesn't support that] > > > > > > Who architects an entire configuration that is dependent o

[petsc-dev] petsc-dev on bitbucket

> > tags are no good. we implrement branches in different clones. > Which is not a better model. > You could argue that we should throw away branches in clones have all > clones in a single branch - and change our workflow. > Yes, I would suggest this. But I think this will be too confusing to

[petsc-dev] petsc-dev on bitbucket

On Wed, 8 Feb 2012, Sean Farley wrote: > > > > Hell, if you *really* want to, just create the account: petsc-release(s) > > then the URL would be > > > > http://bitbucket.org/petsc-release/petsc-3.1 > > > > Actually, it's even easier than that: > > https://bitbucket.org/petsc/petsc-dev/downloads

[petsc-dev] petsc-dev on bitbucket

> > Isn't Matt pissed off with this? 'BuildSystem' -> 'buildsystem' >> >> [I thought the naming scheme with caps was important - and looks like >> bitbucket doesn't support that] > > > Who architects an entire configuration that is dependent on the file > system? Both mac and windows, by default, a

[petsc-dev] petsc-dev on bitbucket

> > Isn't Matt pissed off with this? 'BuildSystem' -> 'buildsystem' > > [I thought the naming scheme with caps was important - and looks like > bitbucket doesn't support that] Who architects an entire configuration that is dependent on the file system? Both mac and windows, by default, are case-i

[petsc-dev] petsc-dev on bitbucket

On Thu, Feb 9, 2012 at 20:19, Satish Balay wrote: > Isn't Matt pissed off with this? 'BuildSystem' -> 'buildsystem' > > [I thought the naming scheme with caps was important - and looks like > bitbucket doesn't support that] > He uses a Mac now, so evidently he doesn't care about capitalization.

[petsc-dev] petsc-dev on bitbucket

On Tue, 7 Feb 2012, Sean Farley wrote: > Also, BuildSystem is here: > > https://bitbucket.org/petsc/buildsystem Isn't Matt pissed off with this? 'BuildSystem' -> 'buildsystem' [I thought the naming scheme with caps was important - and looks like bitbucket doesn't support that] Satish

[petsc-dev] petsc-dev on bitbucket

> > Let's all stop using google and switch to 1998 Yahoo. It's so much easier > to find things by navigating a hierarchy. > Bam! That. Just. Happened. -- next part -- An HTML attachment was scrubbed... URL:

[petsc-dev] petsc-dev on bitbucket

On Wed, Feb 8, 2012 at 11:31, Barry Smith wrote: > Yes. If you can't have that then it is a pretty crappy system. Sort of > like IBM 360 where you only had a root directory with a truckload of files > in it. In excusable in 2012 (or even 1972). Let's all stop using google and switch to 1998 Y

[petsc-dev] petsc-dev on bitbucket

On Wed, Feb 8, 2012 at 21:05, Matthew Knepley wrote: > I would be alright with any grouping strategy, be it > directories, tags, etc. I think this is orthogonal to Mercurial. > All I would want is tags. Hierarchical directory trees are so 1970s. -- next part -- An HTML at

[petsc-dev] petsc-dev on bitbucket

On Feb 8, 2012, at 2:55 PM, Jed Brown wrote: > On Wed, Feb 8, 2012 at 21:05, Matthew Knepley wrote: > I would be alright with any grouping strategy, be it > directories, tags, etc. I think this is orthogonal to Mercurial. > > All I would want is tags. Hierarchical directory trees are so 1970s.

[petsc-dev] petsc-dev on bitbucket

> > Hell, if you *really* want to, just create the account: petsc-release(s) > then the URL would be > > http://bitbucket.org/petsc-release/petsc-3.1 > Actually, it's even easier than that: https://bitbucket.org/petsc/petsc-dev/downloads which provides downloads for all taged changesets. ---

[petsc-dev] petsc-dev on bitbucket

On Wed, Feb 8, 2012 at 11:32 AM, Sean Farley wrote: > No I mean I want >> >> petsc/releases/petsc-3.1 >> petsc/tools/parsing/BarrysNewHTMLMunger >> > > Sounds like you want a "traditional filesystem hierarchy" and like I said > before, your request will fall on deaf ears. This is the same req

[petsc-dev] petsc-dev on bitbucket

> > Generally you want fewer people with root access the closer you get to the > root directory since the more harm they can do. So for example > petsc/releases would only have Satish and one other with admin. Which is perfectly fine and easy to set up now. Hell, if you *really* want to, just cre

[petsc-dev] petsc-dev on bitbucket

> > Yes. If you can't have that then it is a pretty crappy system. Sort of > like IBM 360 where you only had a root directory with a truckload of files > in it. In excusable in 2012 (or even 1972). You're absolutely right. I mean, what's the point of even having files with code in them? I want to

[petsc-dev] petsc-dev on bitbucket

On Feb 8, 2012, at 10:44 AM, Matthew Knepley wrote: > On Wed, Feb 8, 2012 at 9:39 AM, Barry Smith wrote: > > > and have a hierarchy of managers of the repositories > > I don't know why we need a hierarchy of managers, but we can have individual > managers with admin priv. Generally you

[petsc-dev] petsc-dev on bitbucket

> > No I mean I want > > petsc/releases/petsc-3.1 > petsc/tools/parsing/BarrysNewHTMLMunger > Sounds like you want a "traditional filesystem hierarchy" and like I said before, your request will fall on deaf ears. This is the same request that mercurial-dev gets from people switching from subve

[petsc-dev] petsc-dev on bitbucket

On Feb 8, 2012, at 11:11 AM, Matthew Knepley wrote: > On Wed, Feb 8, 2012 at 10:54 AM, Sean Farley wrote: > There is only a 1-level hierarchy based on a top level account. Sean created > 'petsc' for our stuff. We can create many, so that > we have 'petsc-release', 'petsc-private', etc. if we wa

[petsc-dev] petsc-dev on bitbucket

On Wed, Feb 8, 2012 at 10:54 AM, Sean Farley wrote: > There is only a 1-level hierarchy based on a top level account. Sean >> created 'petsc' for our stuff. We can create many, so that >> we have 'petsc-release', 'petsc-private', etc. if we want. Of course, I >> want traditional hierarchy, and wi

[petsc-dev] petsc-dev on bitbucket

> > There is only a 1-level hierarchy based on a top level account. Sean > created 'petsc' for our stuff. We can create many, so that > we have 'petsc-release', 'petsc-private', etc. if we want. Of course, I > want traditional hierarchy, and will file a feature request. > If you phrase it like tha

[petsc-dev] petsc-dev on bitbucket

> > Push two places manually? WTF, presumably Mecurial is feature rich > enough that you could automate the whole process of "pushing to 2 places"? > Already ahead of you, B-man. I added a hook to petsc-dev on petsc.cs.iit.edu. Someone should test that it works (by pushing to petsc.cs.iit.edu)

[petsc-dev] petsc-dev on bitbucket

On Wed, Feb 8, 2012 at 9:39 AM, Barry Smith wrote: > > On Feb 8, 2012, at 9:06 AM, Matthew Knepley wrote: > > > On Wed, Feb 8, 2012 at 7:54 AM, Barry Smith wrote: > > > > On Feb 8, 2012, at 6:43 AM, Satish Balay wrote: > > > > > On Tue, 7 Feb 2012, Barry Smith wrote: > > > > > >> > > >> On Feb 7

[petsc-dev] petsc-dev on bitbucket

On Feb 8, 2012, at 9:06 AM, Matthew Knepley wrote: > On Wed, Feb 8, 2012 at 7:54 AM, Barry Smith wrote: > > On Feb 8, 2012, at 6:43 AM, Satish Balay wrote: > > > On Tue, 7 Feb 2012, Barry Smith wrote: > > > >> > >> On Feb 7, 2012, at 9:09 PM, Sean Farley wrote: > >> > >>> I'm sure Jed (or Matt

[petsc-dev] petsc-dev on bitbucket

On Wed, Feb 8, 2012 at 7:54 AM, Barry Smith wrote: > > On Feb 8, 2012, at 6:43 AM, Satish Balay wrote: > > > On Tue, 7 Feb 2012, Barry Smith wrote: > > > >> > >> On Feb 7, 2012, at 9:09 PM, Sean Farley wrote: > >> > >>> I'm sure Jed (or Matt in his prime) could have run over to IIT and > restarte

[petsc-dev] petsc-dev on bitbucket

On Wed, 8 Feb 2012, Barry Smith wrote: > >> Besides who the heck set up the machine so it cannot be started > >> remotely? Should have used an Apple machine :-) > > > > > > It was a human error [when you tell something to shutdown - it should not > > automatically restart]. > > > > yeah -

[petsc-dev] petsc-dev on bitbucket

On Feb 8, 2012, at 6:43 AM, Satish Balay wrote: > On Tue, 7 Feb 2012, Barry Smith wrote: > >> >> On Feb 7, 2012, at 9:09 PM, Sean Farley wrote: >> >>> I'm sure Jed (or Matt in his prime) could have run over to IIT and >>> restarted the machine in less time than this :-) >>> >>> Sure, and lik

[petsc-dev] petsc-dev on bitbucket

On Tue, 7 Feb 2012, Barry Smith wrote: > > On Feb 7, 2012, at 9:09 PM, Sean Farley wrote: > > > I'm sure Jed (or Matt in his prime) could have run over to IIT and > > restarted the machine in less time than this :-) > > > > Sure, and like everybody else they would have had to wait outside unti

[petsc-dev] petsc-dev on bitbucket

Rich Martineau volunteers to knock down any barriers (including locked doors) between PETSc and the wider world. Apparently, he's still not past his prime. Dmitry. On Tue, Feb 7, 2012 at 10:23 PM, Barry Smith wrote: > > On Feb 7, 2012, at 9:09 PM, Sean Farley wrote: > > > I'm sure Jed (or Matt i

[petsc-dev] petsc-dev on bitbucket

On Feb 7, 2012, at 9:09 PM, Sean Farley wrote: > I'm sure Jed (or Matt in his prime) could have run over to IIT and restarted > the machine in less time than this :-) > > Sure, and like everybody else they would have had to wait outside until they > had keys :-) Those guys are very resourc

[petsc-dev] petsc-dev on bitbucket

The lab opens almost all the time - graduate students stay in the lab 7x24 ... Hong On Tue, Feb 7, 2012 at 9:09 PM, Sean Farley wrote: > I'm sure Jed (or Matt in his prime) could have run over to IIT and >> restarted the machine in less time than this :-) > > > Sure, and like everybody else the

[petsc-dev] petsc-dev on bitbucket

> > I'm sure Jed (or Matt in his prime) could have run over to IIT and > restarted the machine in less time than this :-) Sure, and like everybody else they would have had to wait outside until they had keys :-) -- next part -- An HTML attachment was scrubbed... URL:

[petsc-dev] petsc-dev on bitbucket

On Feb 7, 2012, at 8:14 PM, Sean Farley wrote: > "Yoo, i've switched petsc-dev over to bitbucket since petsc.cs.itt.edu is > down pull/push from https://bitbucket.org/petsc/petsc-dev > > Sean" - Barry impersonating me I'm sure Jed (or Matt in his prime) could have run over to IIT and re

[petsc-dev] petsc-dev on bitbucket

On Tue, Feb 7, 2012 at 8:14 PM, Sean Farley wrote: > "Yoo, i've switched petsc-dev over to bitbucket since petsc.cs.itt.edu is > down pull/push from https://bitbucket.org/petsc/petsc-dev > > Sean" - Barry impersonating me > I have pushed to bring it up to date with the latest master. Mat

[petsc-dev] petsc-dev on bitbucket

"Yoo, i've switched petsc-dev over to bitbucket since petsc.cs.itt.edu is down pull/push from https://bitbucket.org/petsc/petsc-dev Sean" - Barry impersonating me Since petsc.cs is down, I don't have everyone's public SSH key. For now, if you need push access, just sign up for a free bitbucke