On 2021-05-19 08:36, Patrick Sanan did write:
> Cool - I didn't know about this approach - If you still have your experiments
> sitting around, can you put numbers on what kind of space savings are we
> talking about vs the dumb approach (I have an independent clone for every
> branch I'm
Lawrence,
Oh, I always use that, (even now) my prompt is miles long. Didn't help me
at all, I still messed up constantly; my brain ignores what my eyes clearly
see. I need more than a clear sign post telling me where I am, I need a hammer
that hits me whenever I do something wrong in
> On 19 May 2021, at 15:38, Barry Smith wrote:
>
> I tried the multiple clone approach first but found I was constantly
> thinking I was in a different branch than I was in as I went between clones
> and messing up my working directory and getting confused and frustrated. So I
>
I tried the multiple clone approach first but found I was constantly thinking
I was in a different branch than I was in as I went between clones and messing
up my working directory and getting confused and frustrated. So I developed
some of my tools because I was unable to utilize my brain
Cool - I didn't know about this approach - If you still have your experiments
sitting around, can you put numbers on what kind of space savings are we
talking about vs the dumb approach (I have an independent clone for every
branch I'm interested in working on simultaneously)?
@Barry - thanks
A. I remember your email about it, and I even have it checked out.
I didn't get it at the time, but necessity is not only them other of
invention, but of learning.
Scott
On 2021-05-18 18:39, Barry Smith did write:
>
> Scott,
>
> My solution to working with multiple PETSc branches
Scott,
My solution to working with multiple PETSc branches without the agonizing
pain is g...@gitlab.com:petsc/petscgitbash.git
One could argue it is too particular to Barry's specific workflow but
perhaps it has ideas/code that can be stolen for others. It could also
potentially
With later versions of git, `git branch` shows branches are also setup
as worktree's which I personally like quite a bit. Also, thinking
through the worktree workflow has forced me to improve my own workflow
in terms of directory naming discipline (but that is probably just me
who had far too
I don't follow the advantage over lightweight clones, such as:
$ git clone --branch=release --reference petsc gitlab:petsc/petsc petsc-release
Cloning into 'petsc-release'...
remote: Enumerating objects: 261, done.
remote: Counting objects: 100% (261/261), done.
remote: Compressing objects: 100%
