On Fri, Feb 5, 2021 at 9:06 PM Steven A. Falco wrote:
>
> On 2/5/21 1:05 PM, Jonathan Wakely wrote:
> > On 05/02/21 10:08 -0500, Steven A. Falco wrote:
> >> I see that the master to main conversion has happened. I'd like to know
> >> the recommended way to deal with that.
> >>
> >> Currently, I'
On Fri, Feb 5, 2021 at 3:06 PM Jonathan Wakely
wrote:
>
> On 05/02/21 10:08 -0500, Steven A. Falco wrote:
> >I see that the master to main conversion has happened. I'd like to know the
> >recommended way to deal with that.
> >
> >Currently, I'm doing:
> >
> >git fetch --all
> >git remote prune o
On Fri, 2021-02-05 at 18:05 +, Jonathan Wakely wrote:
>
> I think this is all you need:
>
> git fetch -p
>
> git checkout rawhide
>
> Then optionally:
>
> git branch -d master
Thank you !
--
Sérgio M. B.
___
devel mailing list -- devel@lists.
On 2/5/21 1:05 PM, Jonathan Wakely wrote:
On 05/02/21 10:08 -0500, Steven A. Falco wrote:
I see that the master to main conversion has happened. I'd like to know the
recommended way to deal with that.
Currently, I'm doing:
git fetch --all
git remote prune origin
git remote set-head origin -a
On 05/02/21 10:08 -0500, Steven A. Falco wrote:
I see that the master to main conversion has happened. I'd like to know the
recommended way to deal with that.
Currently, I'm doing:
git fetch --all
git remote prune origin
git remote set-head origin -a
git checkout main
The above sets origin/
I see that the master to main conversion has happened. I'd like to know the
recommended way to deal with that.
Currently, I'm doing:
git fetch --all
git remote prune origin
git remote set-head origin -a
git checkout main
The above sets origin/HEAD to rawhide
Question 1: Is that the right se
