On Sun, 18 Nov 2012, Shri wrote:
> Satish,
>What's happening with the private repos hosted on petsc.cs.iit.edu? I had
> a private repo there for my Ph.D. project (ts_emt). Although I don't need it
> anymore, I just wanted to check if it was backed up somehow.
Yes - I do have backups - and c
Satish,
What's happening with the private repos hosted on petsc.cs.iit.edu? I had a
private repo there for my Ph.D. project (ts_emt). Although I don't need it
anymore, I just wanted to check if it was backed up somehow.
Thanks,
Shri
On Nov 18, 2012, at 9:43 PM, Satish Balay wrote:
> On Sat,
On Sat, 17 Nov 2012, Barry Smith wrote:
>
> On Nov 17, 2012, at 10:52 AM, Jed Brown wrote:
>
> > On Sat, Nov 17, 2012 at 11:48 AM, Satish Balay wrote:
> > \
> >
> > [I don't think its appropriate to make this change for a petsc-3.3 patch
> > update.]
> >
> > Okay, what if we start using sub
On Nov 17, 2012, at 10:52 AM, Jed Brown wrote:
> On Sat, Nov 17, 2012 at 11:48 AM, Satish Balay wrote:
> \
>
> [I don't think its appropriate to make this change for a petsc-3.3 patch
> update.]
>
> Okay, what if we start using subrepos with petsc-dev -> buildsystem and let
> petsc-release
On Sat, Nov 17, 2012 at 11:48 AM, Satish Balay wrote:
> This presumably merged the new head [in petsc-release/buildsystem]
> that I created with the new head that Barry created in his clone?
>
> BTW: am I correct in assuming that this head won't get pushed to
> buildsystem unless 'petsc-release -
On Sat, Nov 17, 2012 at 11:19 AM, Satish Balay wrote:
> I guess it could b:
>
> - I make changes to petsc-release/buildsystem, commit
>
This create a new head in petsc-release/buildsystem (but not in
petsc-release).
> push petsc-release
> [error with buildsystem push - so merge with petsc-rel
On Sat, 17 Nov 2012, Jed Brown wrote:
> On Sat, Nov 17, 2012 at 11:19 AM, Satish Balay wrote:
>
> > I guess it could b:
> >
> > - I make changes to petsc-release/buildsystem, commit
> >
>
> This create a new head in petsc-release/buildsystem (but not in
> petsc-release).
>
>
> > push petsc-re
On Sat, 17 Nov 2012, Satish Balay wrote:
> On Sat, 17 Nov 2012, Satish Balay wrote:
>
> > On Fri, 16 Nov 2012, Barry Smith wrote:
> >
> > >
> > > On Nov 16, 2012, at 3:45 PM, Jed Brown wrote:
> > >
> > > > I think we could nicely do petsc-dev, petsc-release, and one
> > > > buildsystem manag
On Sat, 17 Nov 2012, Satish Balay wrote:
> On Fri, 16 Nov 2012, Barry Smith wrote:
>
> >
> > On Nov 16, 2012, at 3:45 PM, Jed Brown wrote:
> >
> > > I think we could nicely do petsc-dev, petsc-release, and one buildsystem
> > > managed as a subrepo.
> >
> >I'm willing to try this.
>
> S
On Fri, 16 Nov 2012, Barry Smith wrote:
>
> On Nov 16, 2012, at 3:45 PM, Jed Brown wrote:
>
> > I think we could nicely do petsc-dev, petsc-release, and one buildsystem
> > managed as a subrepo.
>
>I'm willing to try this.
So how do we proceed with it?
- commit buildsystem as subrepo of
On Fri, Nov 16, 2012 at 6:22 PM, Jed Brown wrote:
> Agreed, but git got branches right the first time (stable within weeks or
> months of mkdir)
Cool.
> and hg has had many years to just copy, yet the feature
> still has odd quirks. Hopefully it will get better now that the devs are
> finally us
Agreed, but git got branches right the first time (stable within weeks or
months of mkdir) and hg has had many years to just copy, yet the feature
still has odd quirks. Hopefully it will get better now that the devs are
finally using it themselves, but I foresee a long road unless they give up
on t
I think we could nicely do petsc-dev, petsc-release, and one buildsystem
managed as a subrepo.
We could do one petsc too, bit hg branches/bookmarks kinda suck so I don't
think it would be as nice.
On Nov 16, 2012 4:32 PM, "Satish Balay" wrote:
> to rephrase - do we do:
>
> 1. petsc, buildsystem,
I have been using bookmarks to label subprojects locally and in my forks of
petsc.
Admittedly, that usage was rather pedestrian, but at least at that level
they seemed to be fine.
Dmitry.
On Fri, Nov 16, 2012 at 3:51 PM, Barry Smith wrote:
>
> On Nov 16, 2012, at 3:45 PM, Jed Brown wrote:
>
>
On Fri, Nov 16, 2012 at 3:45 PM, Jed Brown wrote:
> I think we could nicely do petsc-dev, petsc-release, and one buildsystem
> managed as a subrepo.
>
> We could do one petsc too, bit hg branches/bookmarks kinda suck so I don't
> think it would be as nice.
Branches in mercurial are fine (it's wha
On Nov 16, 2012, at 3:45 PM, Jed Brown wrote:
> I think we could nicely do petsc-dev, petsc-release, and one buildsystem
> managed as a subrepo.
I'm willing to try this.
Barry
>
> We could do one petsc too, bit hg branches/bookmarks kinda suck so I don't
> think it would be as nice.
to rephrase - do we do:
1. petsc, buildsystem, petsc-release, buildsystem-release
2. petsc-dev, buildsystem-dev, petsc-release, buildsystem-release
3. petsc-dev, buildsystem, petsc-release, buildsystem-release
4. something else?
satish
On Fri, 16 Nov 2012, Satish Balay wrote:
> Do you want to
Do you want to have the repo name as 'buildsystem' or
'buildsystem-dev'?
note: reclones shouldn't be need for such renames [or url changes] -
but one is free to do that if they want to..
Satish
On Fri, 16 Nov 2012, Barry Smith wrote:
>
> I am not advocating fixing all capitalizations at this
I am not advocating fixing all capitalizations at this time, just
BuildSystems.
Plus we should tell everyone to completely reclone anyways.
Keeping the in consist BuildSystem just to prevent a small number of
temporary hiccups is not a good idea. We're writing PETSc not lapack.
Ba
On Fri, 16 Nov 2012, Barry Smith wrote:
>
> On Nov 16, 2012, at 11:14 AM, Satish Balay wrote:
>
> > I'm in the process of migrating repos from petsc.cs.iit.edu to
> > bitbucket.org, and have to resolve a few organization issues.
> >
> > Restrictions.
> > - all repos should be lowercase
> > - n
On Nov 16, 2012, at 11:14 AM, Satish Balay wrote:
> I'm in the process of migrating repos from petsc.cs.iit.edu to
> bitbucket.org, and have to resolve a few organization issues.
>
> Restrictions.
> - all repos should be lowercase
> - no subdir organization possible [like
> http://petsc.cs.iit
I'm in the process of migrating repos from petsc.cs.iit.edu to
bitbucket.org, and have to resolve a few organization issues.
Restrictions.
- all repos should be lowercase
- no subdir organization possible [like
http://petsc.cs.iit.edu/petsc/externalpackages/]
1. Since we are forced to change rep
22 matches
Mail list logo
