You are right, John. I did not read it carefully enough.
Guillermo
On Sun, 9 Apr 2023 at 05:38, John H Palmieri wrote:
> I have found the instructions at
> https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md
> useful for me, as someone used to the old trac i
another option is to use gh tool from GitHub.
gh pr checkout 35414
would do the same as
git fetch foo pull/35414/head:pr35414 && git checkout pr35414
On Sun, Apr 9, 2023 at 4:38 AM John H Palmieri wrote:
>
> I have found the instructions at
> https://github.com/sagemath/trac-to-git
I have found the instructions at
https://github.com/sagemath/trac-to-github/blob/master/docs/Migration-Trac-to-Github.md
useful for me, as someone used to the old trac interface.
On Saturday, April 8, 2023 at 1:23:06 PM UTC-7 G. M.-S. wrote:
>
> Thanks Dima and Drew.
>
> I had the very same q
Thanks Dima and Drew.
I had the very same question, but zero ways for doing it, so I did not dare
ask…
Guillermo
On Sat, 8 Apr 2023 at 22:14, Dima Pasechnik wrote:
>
> On Sat, 8 Apr 2023, 20:24 Drew Shotwell, wrote:
>
>> I'm looking into working on an issue in git, and I'm wondering how to
>>
On Sat, 8 Apr 2023, 20:24 Drew Shotwell, wrote:
> I'm looking into working on an issue in git, and I'm wondering how to
> properly go about testing someone else's branch. Let's take for instance
> https://github.com/sagemath/sage/pull/35414.
suppose you have remote foo set to
https://github.com
I'm looking into working on an issue in git, and I'm wondering how to
properly go about testing someone else's branch. Let's take for instance
https://github.com/sagemath/sage/pull/35414. Essentially what I want to do
is get the code changes from the forked branch
videlec:complex-root-of-to-alg
