[petsc-dev] Location for tutorial codes

[Satish Balay]

Barry,

there are 2 ways of grouping - one is a prefix, the other is a subdir.

The release repos were already grouped with a common prifix - so it
didn't need a subdir regrouping. [however this forces url changes for
folks with these clones]. Plus the names don't pass your check for
duplicate info.

petsc-releases/petsc-release-2.3.1

Tutorials were not already grouped [so either a rename or a subdir was
appropriate change]

If release clones were to be better grouped, perhaps the following
organization is better.

releases/petsc-2.3.1
releases/petsc-3.0.0
releases/BuildSystem-2.3.1
releases/BuildSystem-3.0.0

[but this requires renaming the parent url aswell as clone names [since some of us
usually use the same name for clones as the master repo]

Satish


On Fri, 7 May 2010, Barry Smith wrote:

> 
>   I have moved the tutorials into a tutorials subdirectory (I did not change the name of the individual directories so they still end in TutorialCode.
> 
> 
>   Also made a BuildSystem-releases and petsc-releases and move the old releases into there. People WILL NEED to update there .hg/hgrc for their clones.
> 
>   There is a petsc-dev-for-fixes and petsc-dev-new-solvers and petsc-dev-dalcinl can I delete those?
> 
>    Barry
> 
> 
> On May 7, 2010, at 12:53 PM, Jed Brown wrote:
> 
> > On Fri, 7 May 2010 12:36:53 -0500, Barry Smith <bsmith at mcs.anl.gov> wrote:
> >> 
> >>  Seems reasonable to me. Also repositories of BuildSystem and petsc
> >>  for previous releases could go into two subdirectories
> > 
> > I don't think I can do that sort of thing since I can't log into the
> > machine.  Perhaps one of you can do that, or at least create the new
> > directory (so the URL in my slides will be stable for a while after
> > Monday/Tuesday).
> > 
> > Jed
> 
>