> As subject, where to get sources for 12-stable upgrade now? Is it still > svn or is it git?Probably your choice. But one thing that could bias towards svn is that the svn information spans identifying both the svn and the git material but the git commit does not identify the svn material. For example, via: https://svnweb.freebsd.org/base/stable/12/lib/?sortby=rev&sortdir=down&view=log is the following . . . QUOTE Revision 369260 - Directory Listing Modified Fri Feb 12 21:02:48 2021 UTC (4 hours, 49 minutes ago) by dim test_inf_inputs: Use atf_tc_expect_fail() instead of atf_tc_skip() Reviewed By: lwhsu Differential Revision: https://reviews.freebsd.org/D28396 (cherry picked from commit 4d2edf3af1dbd8a3e7cf1b22343a1ecfc2dd41ba) Fix lib/msun's ctrig_test/test_inf_inputs test case with clang >= 10 This sprinkles a few strategic volatiles in an attempt to defeat clang's optimization interfering with the expected floating-point exception flags. Reported by: lwhsu PR: 244732 (cherry picked from commit ac76bc1145dd7f4476e5d982ce8f355f71015713) Git Hash: f2a88e744701de1b37d7463828f2147f96e39d58 Git Author: arichardson at FreeBSD.org END QUOTE So both -r369260 and git hash-ids are indicated. By contrast, the cgit commit's display does not identify the svn side's -r369260 : QUOTE diff options context: space: mode: author Alex Richardson <arichardson at FreeBSD.org> 2021-01-29 09:28:40 +0000 committer Dimitry Andric <dim at FreeBSD.org> 2021-02-12 20:50:28 +0000 commit f2a88e744701de1b37d7463828f2147f96e39d58 (patch) tree 0db8207a810f40d7f82c2033f8377ed38ce08ba2 parent 9525ccc84e337f4261425fc8fbf9f0de18500a1b (diff) download src-f2a88e744701de1b37d7463828f2147f96e39d58.tar.gz src-f2a88e744701de1b37d7463828f2147f96e39d58.zip test_inf_inputs: Use atf_tc_expect_fail() instead of atf_tc_skip()stable/12 Reviewed By: lwhsu Differential Revision: https://reviews.freebsd.org/D28396 (cherry picked from commit 4d2edf3af1dbd8a3e7cf1b22343a1ecfc2dd41ba) Fix lib/msun's ctrig_test/test_inf_inputs test case with clang >= 10 This sprinkles a few strategic volatiles in an attempt to defeat clang's optimization interfering with the expected floating-point exception flags. Reported by: lwhsu PR: 244732 (cherry picked from commit ac76bc1145dd7f4476e5d982ce8f355f71015713) END QUOTE Matching up stable revisions with releng/12.3/ or release/12.3.0/ in the future would be easier starting from svn material in the first place and would provide identification for git as well. But I've no clue if such would be important to what you might need to do with 12. ==Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)
On Fri, Feb 12, 2021 at 06:11:25PM -0800, Mark Millard via freebsd-stable wrote:>But I've no clue if such would be important to what you might need >to do with 12.you're right, I should have been more detailed. My context is in looking after various 12-stable machines. Basically I'm asking "which is the source for truth now". I'm not a dev so this is non-obvious to me; all i'm interested in is keeping machines up-to-date. I knew stable/13 and current/14 were going to git, but never heard anything about stable/12 or earlier versions. I saw on cgit that stable/12 was there. These older systems weekly update their sources via svn till now, in a cron job. At the time I wrote my message, I saw that svn still works, so was wondering which to use, which has the latest updates. thanks, -- J. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20210213/557b3a69/attachment.sig>
On 13/02/2021 1:11 pm, Mark Millard via freebsd-stable wrote:>> As subject, where to get sources for 12-stable upgrade now? Is it still >> svn or is it git? > > Probably your choice. But one thing that could > bias towards svn is that the svn information > spans identifying both the svn and the git > material but the git commit does not identify > the svn material. For example, via: > > https://svnweb.freebsd.org/base/stable/12/lib/?sortby=rev&sortdir=down&view=log > > is the following . . .... [ Quite lenghty ref earlier email]> ==> Mark Millard > marklmi at yahoo.com > ( dsl-only.net went > away in early 2018-Mar) > > _______________________________________________ > freebsd-stable at freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org" >Thanks for raising the thread. I'm in a similar boat. Though, prior to an update, we'd review the changes via the mailing lists. The main list we used was: https://lists.freebsd.org/pipermail/svn-src-stable-12/ but that appears dead. Normally we'd update fortnightly or trigger an update when there was an incremental patch update to "release" as advised via: https://lists.freebsd.org/pipermail/svn-src-release/ suspect also dead. Suggestion - final entry in dead lists to provide a pointer to its git equivalent? I suspect that https://lists.freebsd.org/pipermail/dev-commits-src-branches/2021-January/thread.html is the stable-12 equivalent but are incremental patch releases also available here? As a change management task, I would hope that a mapping between svnlite and git would've become available for FreeBSD users, similar to the cvs to svnlite migration. I guess we need to create a test machine to figure out the commands we need for git to replace what we use in the scripts (mainly "update -r "{$DATE}", diff and log along with the incantation to create a git repository). I wish that I could articulate the reason to management that FreeBSD is making the move from svn to git? Is there a timeline when svn for stable-12 /usr/src disappears? (I'm dreading a ports move to a git paradigm...)