Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Dec 2020 12:05:28 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Nathan Whitehorn <nwhitehorn@freebsd.org>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>
Subject:   Re: HEADS UP: FreeBSD src repo transitioning to git this weekend
Message-ID:  <CANCZdfrF0B7uux_neg-4XGn2UCDd4noUm7zP_icHnrpZUgmzzA@mail.gmail.com>
In-Reply-To: <31ab8015-a0c4-af77-0ead-a17da0f88f1d@freebsd.org>
References:  <CANCZdfrUsaw5jpN1ybpk0ADXdQYam0_NO0mPJd0-FMbuxPruhw@mail.gmail.com> <31ab8015-a0c4-af77-0ead-a17da0f88f1d@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 17, 2020 at 12:01 PM Nathan Whitehorn <nwhitehorn@freebsd.org>
wrote:

>
>
> On 12/16/20 7:46 PM, Warner Losh wrote:
> > Greetings,
> >
> > The FreeBSD project will be moving it's source repo from subversion to
> git
> > starting this this weekend. The docs repo was moved 2 weeks ago. The
> ports
> > repo will move at the end of March, 2021 due to timing issues.
> >
> > The short version is that we're switching the version control we're
> using.
> > This switch will preserve much of the current FreeBSD development
> workflow.
> > After the switch, the subversion repo will become almost read-only. All
> > future work will be done in git, however as a transition aide we'll be
> > replaying the MFCs to stable/11, stable/12 and the related releng
> branches
> > for the life of those branches.
> >
> > For more detailed information, please see
> > https://github.com/bsdimp/freebsd-git-docs/ for the current
> documentation.
> >
> > Please see https://wiki.freebsd.org/git for the latest detailed schedule
> > (please note that this schedule is subject to change).
> >
> > Warner
> > _______________________________________________
> > freebsd-current@freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "
> freebsd-current-unsubscribe@freebsd.org"
> >
>
> One question I didn't see in the (excellent!) docs is whether we should
> be PGP-signing commits or not. Is that encouraged?
>

We've not started doing that in general. I don't think signing would cause
issues, but since it is a bit of an unknown, we've not taken a position on
this.

Warner (on behalf of the git working group)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrF0B7uux_neg-4XGn2UCDd4noUm7zP_icHnrpZUgmzzA>