Re: Plans for git

2020-09-24 Thread Alexander Leidinger
Quoting Christian Weisgerber (from Mon, 21 Sep 2020 21:55:00 - (UTC)): Well, I was asking for a summary. For instance, I don't know if the Git migration is merely a switch of the version control system or what other changes will be layered on top of it as a matter of course, e.g. will th

Re: Plans for git

2020-09-21 Thread Steffen Nurpmeso
Warner Losh wrote in : |On Mon, Sep 21, 2020 at 2:55 PM Steffen Nurpmeso \ |wrote: |> Lev Serebryakov wrote in |> <23e7fc1c-6769-ceaf-4089-46e5cc575...@freebsd.org>: |>|On 19.09.2020 19:05, Bakul Shah wrote: |>|>> These are the main ones. The three down sides are lack of $FreeBSD$ \ |>|>>

Re: Plans for git

2020-09-21 Thread Christian Weisgerber
On 2020-09-21, Pete Wright wrote: > I believe the most detailed report on this was in the 2020-04 quarterly > status report: > https://www.freebsd.org/news/status/report-2020-04-2020-06.html#Git-Migration-Working-Group I saw that at the time. It basically says that the conversion of the reposi

Re: Plans for git

2020-09-21 Thread Warner Losh
On Mon, Sep 21, 2020 at 2:55 PM Steffen Nurpmeso wrote: > Lev Serebryakov wrote in > <23e7fc1c-6769-ceaf-4089-46e5cc575...@freebsd.org>: > |On 19.09.2020 19:05, Bakul Shah wrote: > |>> These are the main ones. The three down sides are lack of $FreeBSD$ \ > |>> support > |>> and tags in gener

Re: Plans for git

2020-09-21 Thread Steffen Nurpmeso
Lev Serebryakov wrote in <23e7fc1c-6769-ceaf-4089-46e5cc575...@freebsd.org>: |On 19.09.2020 19:05, Bakul Shah wrote: |>> These are the main ones. The three down sides are lack of $FreeBSD$ \ |>> support |>> and tags in general. |> |> Can a git hook be used for this? | |git filters could b

Re: Plans for git

2020-09-21 Thread Pete Wright
On 9/21/20 12:49 PM, Christian Weisgerber wrote: On 2020-09-21, Alexander Leidinger wrote: In my opinion the people which drive this didn't keep it behind closed curtains, and they went step by step more public, as they made progress. To me it looks like now, that they have something which

Re: Plans for git

2020-09-21 Thread Lucas Nali de Magalhães
> On Sep 21, 2020, at 4:22 AM, Alexander Leidinger > wrote: > > Quoting Pete Wright (from Sun, 20 Sep 2020 08:41:13 > -0700): > > Not responding to Pete directly, but in general to this topic with some parts > of what Pete considers good as something to hook into. > making quarterly r

Re: Plans for git

2020-09-21 Thread Christian Weisgerber
On 2020-09-21, Alexander Leidinger wrote: > In my opinion the people which drive this didn't keep it behind > closed curtains, and they went step by step more public, as they > made progress. To me it looks like now, that they have something > which is presentable to the world (and not only to c

Re: Plans for git

2020-09-21 Thread Alexander Leidinger
Quoting Pete Wright (from Sun, 20 Sep 2020 08:41:13 -0700): Not responding to Pete directly, but in general to this topic with some parts of what Pete considers good as something to hook into. making quarterly reports about this for almost a years as well. We put out calls for people to h

Re: Plans for git

2020-09-20 Thread Adrian Chadd
On Sun, 20 Sep 2020 at 15:37, Rick Macklem wrote: > Christian Weisgerber wrote: > > On 2020-09-19, Zaphod Beeblebrox wrote: > > > > > Hrm. Maybe what I hear others saying, tho, and not entirely being > replied > > > to is just a nice concise document of the why. What I hear you saying > is > >

Re: Plans for git

2020-09-20 Thread Rick Macklem
Christian Weisgerber wrote: > On 2020-09-19, Zaphod Beeblebrox wrote: > > > Hrm. Maybe what I hear others saying, tho, and not entirely being replied > > to is just a nice concise document of the why. What I hear you saying is > > that GIT has momentum and that it's popular... (and I accept tha

Re: Plans for git

2020-09-20 Thread Russell L. Carter
On 2020-09-20 12:28, Andriy Gapon wrote: > Just my +100500 to this. > > On 20/09/2020 18:03, Christian Weisgerber wrote: >> On 2020-09-19, Zaphod Beeblebrox wrote: >> >>> Hrm. Maybe what I hear others saying, tho, and not entirely being replied >>> to is just a nice concise document of the why.

Re: Plans for git

2020-09-20 Thread Andriy Gapon
Just my +100500 to this. On 20/09/2020 18:03, Christian Weisgerber wrote: > On 2020-09-19, Zaphod Beeblebrox wrote: > >> Hrm. Maybe what I hear others saying, tho, and not entirely being replied >> to is just a nice concise document of the why. What I hear you saying is >> that GIT has momentu

Re: Plans for git

2020-09-20 Thread Lev Serebryakov
On 19.09.2020 19:05, Bakul Shah wrote: >> These are the main ones. The three down sides are lack of $FreeBSD$ support >> and tags in general. > > Can a git hook be used for this? git filters could be used for that, problem is it should be local configuration. You could not configure filters in

Re: Plans for git

2020-09-20 Thread Warner Losh
On Sun, Sep 20, 2020 at 9:41 AM Pete Wright wrote: > > >> making quarterly reports about this for almost a years as well. We put > out > >> calls for people to help with the efforts about the same time. We have > >> tried at every step of the way to be open and honest that this was > going to > >

Re: Plans for git

2020-09-20 Thread Steve Kargl
On Sun, Sep 20, 2020 at 08:41:13AM -0700, Pete Wright wrote: > > > > making quarterly reports about this for almost a years as well. We put out > > > calls for people to help with the efforts about the same time. We have > > > tried at every step of the way to be open and honest that this was goin

Re: Plans for git

2020-09-20 Thread Pete Wright
making quarterly reports about this for almost a years as well. We put out calls for people to help with the efforts about the same time. We have tried at every step of the way to be open and honest that this was going to happen. All developer centric communications I would argue that qua

Re: Plans for git

2020-09-20 Thread Christian Weisgerber
On 2020-09-19, Zaphod Beeblebrox wrote: > Hrm. Maybe what I hear others saying, tho, and not entirely being replied > to is just a nice concise document of the why. What I hear you saying is > that GIT has momentum and that it's popular... (and I accept that --- it is > evidently true), but the

Re: Plans for git

2020-09-20 Thread Rodney W. Grimes
> On Sat, Sep 19, 2020, 2:44 PM Lucas Nali de Magalh?es > wrote: > > > Just My 2?? > > > > On Sep 3, 2020, at 5:19 PM, Warner Losh wrote: > > > > ?On Thu, Sep 3, 2020 at 1:32 PM Chris wrote: > > > > On 2020-09-03 11:33, Kristof Provost wrote: > > > > On 3 Sep 2020, at 19:56, Chris wrote: > > >

Re: Plans for git

2020-09-20 Thread Tomoaki AOKI
Hi! Thanks for clarification, Warner. Focusing on downsides, I feel the second is fundamental. Running (incremental) count is important especially for non-developers like me (or developers not having commit bit) to report problems via ML. It clarifies revision ranges in shorter and clearer form.

Re: Plans for git

2020-09-19 Thread Warner Losh
On Sat, Sep 19, 2020, 2:44 PM Lucas Nali de Magalhães wrote: > Just My 2¢… > > On Sep 3, 2020, at 5:19 PM, Warner Losh wrote: > > On Thu, Sep 3, 2020 at 1:32 PM Chris wrote: > > On 2020-09-03 11:33, Kristof Provost wrote: > > On 3 Sep 2020, at 19:56, Chris wrote: > > Why was the intention to s

Re: Plans for git

2020-09-19 Thread Lucas Nali de Magalhães
Just My 2¢… > On Sep 3, 2020, at 5:19 PM, Warner Losh wrote: > > On Thu, Sep 3, 2020 at 1:32 PM Chris wrote: > >>> On 2020-09-03 11:33, Kristof Provost wrote: >>> On 3 Sep 2020, at 19:56, Chris wrote: Why was the intention to switch NOT announced as such MUCH sooner? >>> There was

Re: Plans for git

2020-09-19 Thread Zaphod Beeblebrox
Actually, frankly, yes. Nearly the first cogent summary I've found so far. On Sat, Sep 19, 2020 at 2:22 AM Warner Losh wrote: > > > On Fri, Sep 18, 2020, 11:31 PM Zaphod Beeblebrox > wrote: > >> Hrm. Maybe what I hear others saying, tho, and not entirely being >> replied to is just a nice con

Re: Plans for git

2020-09-19 Thread Warner Losh
On Sat, Sep 19, 2020, 10:05 AM Bakul Shah wrote: > On Sep 18, 2020, at 11:21 PM, Warner Losh wrote: > > > > These are the main ones. The three down sides are lack of $FreeBSD$ > support > > and tags in general. > > Can a git hook be used for this? > No. Not really. There is an extension to git

Re: Plans for git

2020-09-19 Thread Steffen Nurpmeso
Bakul Shah wrote in : |On Sep 18, 2020, at 11:21 PM, Warner Losh wrote: |> |> These are the main ones. The three down sides are lack of $FreeBSD$ \ |> support |> and tags in general. | |Can a git hook be used for this? I use a git pre-commit hook to fake-update SCCS IDs for my web site (

Re: Plans for git

2020-09-19 Thread Ed Maste
On Sat, 19 Sep 2020 at 12:06, Bakul Shah wrote: > > The cgit-beta.FreeBSD.org and github trees are not identical the last > time I looked (mainly in meta data). Any reason for not keeping them > identical? I switched from the github tree to the cgit-beta tree. The current GitHub mirror is missing

Re: Plans for git

2020-09-19 Thread Bakul Shah
On Sep 18, 2020, at 11:21 PM, Warner Losh wrote: > > These are the main ones. The three down sides are lack of $FreeBSD$ support > and tags in general. Can a git hook be used for this? > > Yes. I've started doing a series of short videos explaining the change, why > we are doing it and what to

Re: Plans for git

2020-09-19 Thread Warner Losh
I've taken the time to clean up this email (which I wrote on my phone last thing yesterday) and expand it a little. https://bsdimp.blogspot.com/2020/09/freebsd-subversion-to-git-migration.html is the result. I'm planning on doing a number of videos about this, as well as blog posts, FreeBSD Journ

Re: Plans for git

2020-09-18 Thread Warner Losh
On Fri, Sep 18, 2020, 11:31 PM Zaphod Beeblebrox wrote: > Hrm. Maybe what I hear others saying, tho, and not entirely being replied > to is just a nice concise document of the why. What I hear you saying is > that GIT has momentum and that it's popular... (and I accept that --- it is > evidentl

Re: Plans for git

2020-09-18 Thread Zaphod Beeblebrox
Hrm. Maybe what I hear others saying, tho, and not entirely being replied to is just a nice concise document of the why. What I hear you saying is that GIT has momentum and that it's popular... (and I accept that --- it is evidently true), but then I hear handwaving about features, but no list of

Re: Plans for git

2020-09-17 Thread Christian Weisgerber
Kyle Evans: > > > This is probably better for a separate thread, but any idea if there > > > > I'm going to regret asking, but what would you need this feature > > for? > > It's not necessarily that bad -- I used to use it for a poor > substitute for git-worktree before I learned about that, for

Re: Plans for git

2020-09-17 Thread Kyle Evans
On Thu, Sep 17, 2020 at 4:15 PM Christian Weisgerber wrote: > > Kyle Evans: > > > > FWIW, I just committed a Got port (devel/got). > > > > This is probably better for a separate thread, but any idea if there > > are plans to eventually support local filesystem cloning in got? > > I wouldn't know.

Re: Plans for git

2020-09-17 Thread Christian Weisgerber
Kyle Evans: > > FWIW, I just committed a Got port (devel/got). > > This is probably better for a separate thread, but any idea if there > are plans to eventually support local filesystem cloning in got? I wouldn't know. I'm going to regret asking, but what would you need this feature for? --

Re: Plans for git

2020-09-17 Thread Kyle Evans
On Thu, Sep 17, 2020 at 3:05 PM Christian Weisgerber wrote: > > On 2020-09-02, Mason Loring Bliss wrote: > > > Just to throw it out there, https://gameoftrees.org/ would be interesting > > to explore for this. > > FWIW, I just committed a Got port (devel/got). > This is probably better for a sep

Re: Plans for git

2020-09-17 Thread Christian Weisgerber
On 2020-09-02, Mason Loring Bliss wrote: > Just to throw it out there, https://gameoftrees.org/ would be interesting > to explore for this. FWIW, I just committed a Got port (devel/got). -- Christian "naddy" Weisgerber na...@mips.inka.de ___

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-04 Thread Warner Losh
Steve, I was wrong to freak out so badly at your suggestion. I can give you an explanation for why but it was wrong for me to do so. I thought that the doc was better than it was and so I couldn't understand and flashed to anger rather than listening. So even so, my tone is well below the standa

Re: Plans for git

2020-09-03 Thread Warner Losh
On Thu, Sep 3, 2020 at 1:32 PM Chris wrote: > On 2020-09-03 11:33, Kristof Provost wrote: > > On 3 Sep 2020, at 19:56, Chris wrote: > >> Why was the intention to switch NOT announced as such MUCH sooner? > >> > > There was discussion about a possible switch to git on the freebsd-git > > mailing >

Re: Plans for git

2020-09-03 Thread Chris
On 2020-09-03 11:33, Kristof Provost wrote: On 3 Sep 2020, at 19:56, Chris wrote: Why was the intention to switch NOT announced as such MUCH sooner? There was discussion about a possible switch to git on the freebsd-git mailing list as early as February 2017: https://lists.freebsd.org/piperma

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-03 Thread Mark Linimon
On Thu, Sep 03, 2020 at 11:40:17AM -0700, Rodney W. Grimes wrote: > To the contrary 5 years ago the project on @developers basically > ran off one of the committers over the very idea of using git > for the project. It was shortly after I returned, so I find it > very ironic that now its all "git

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-03 Thread Rodney W. Grimes
> > > > On Sep 1, 2020, at 10:59 PM, Greg 'groggy' Lehey wrote: > > > > On Tuesday, 1 September 2020 at 13:14:10 -0400, Ed Maste wrote: > >> We've been updating the svn-git converter and pushing out a new > >> converted repo every two weeks, and are now approaching the time where > >> we'd lik

Re: Plans for git

2020-09-03 Thread Kristof Provost
On 3 Sep 2020, at 19:56, Chris wrote: Why was the intention to switch NOT announced as such MUCH sooner? There was discussion about a possible switch to git on the freebsd-git mailing list as early as February 2017: https://lists.freebsd.org/pipermail/freebsd-git/2017-February/92.html Ed

Re: Plans for git

2020-09-03 Thread Chris
On 2020-09-03 11:03, Kurt Jaeger wrote: Hi! Why was the intention to switch NOT announced as such MUCH sooner? Because communicating complex issues which might cause conflict and flame wars etc is not easy. Everyone prefers to hack on code, and possibly procrastinates on the hard stuff 8-} A

Re: Plans for git

2020-09-03 Thread Kurt Jaeger
Hi! > Why was the intention to switch NOT announced as such MUCH sooner? Because communicating complex issues which might cause conflict and flame wars etc is not easy. Everyone prefers to hack on code, and possibly procrastinates on the hard stuff 8-} And all those that do the really heavy work

Re: Plans for git

2020-09-03 Thread Chris
I've been wanting to comment on the git(1) ==> svn(1) switch for some time now. I feel quite strongly about it, and rightfully so for many reasons. But _because_ I feel so strongly about it. I've refrained from doing so. So as to speak in an objective manner -- I'm not _quite_ there yet. But I wan

Re: Plans for git

2020-09-02 Thread Mark Millard
Willem Jan Withagen wjw at digiware.nl wrote on Wed Sep 2 19:50:35 UTC 2020 : > For me Git without Github (or any other reviewing environment) is only > half the change, so I'm wondering where code review will take place. When I look at the likes of, say, https://cgit-beta.freebsd.org/src/log

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread grarpamp
> The underlying initializing 'git init' commit hash must be > signed by security officer key having sufficient human PGP-WoT. > > Git also supports sha-256 soon now, adoption should > be researched from various online article series and > work product before committing plans... > https://lwn.net/A

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Goran Mekić
On Wed, Sep 02, 2020 at 09:47:06AM -0700, Steve Kargl wrote: > Checking out /usr/src as u...@freebsd.org > > svn checkout svn+ssh://u...@svn.freebsd.org/base/head /usr/src git checkout ssh://u...@git.freebsd.org/base/head /usr/src > Checking out /usr/src without freebsd.org account > > svn che

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Mark Linimon
On Wed, Sep 02, 2020 at 08:01:17AM +0200, Kurt Jaeger wrote: > A short intro on git for svn users: > https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view For people like me that will not click on random URLs ... ... just feed "svn to git cheat-sheet" to your favorite search engine. Disclaimer: my initi

Re: Plans for git

2020-09-02 Thread Willem Jan Withagen
On 2-9-2020 21:24, Rainer Duffner wrote: Am 02.09.2020 um 18:22 schrieb Warner Losh : On Sep 2, 2020, at 10:14 AM, Ed Maste wrote: On Wed, 2 Sep 2020 at 02:31, Steve Kargl wrote: A short intro on git for svn users: https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view ROTFL. From the "short

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Rainer Duffner
> Am 02.09.2020 um 18:22 schrieb Warner Losh : > > > >> On Sep 2, 2020, at 10:14 AM, Ed Maste wrote: >> >> On Wed, 2 Sep 2020 at 02:31, Steve Kargl >> wrote: >>> A short intro on git for svn users: https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view >>> >>> ROTFL. From the "sho

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Mason Loring Bliss
On Wed, Sep 02, 2020 at 01:38:09PM -0400, Theron wrote: > After the transition, will FreeBSD base contain the tool for the cloning the > FreeBSD repository (not one of the mirrors?) Just to throw it out there, https://gameoftrees.org/ would be interesting to explore for this. -- Mason Loring Bl

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Dan Langille
resending, because I clearly have no clue. On Wed, Sep 2, 2020, at 2:50 PM, Ian Lepore wrote: > On Wed, 2020-09-02 at 14:45 -0400, Dan Langille wrote: > > On Wed, Sep 2, 2020, at 2:36 PM, Ian Lepore wrote: > > > > > Seriously, Warner? > > > > Yes, seriously. We are adults. Act accordingly. > >

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Dan Langille
On Wed, Sep 2, 2020, at 2:50 PM, Ian Lepore wrote: > On Wed, 2020-09-02 at 14:45 -0400, Dan Langille wrote: > > On Wed, Sep 2, 2020, at 2:36 PM, Ian Lepore wrote: > > > > > Seriously, Warner? > > > > Yes, seriously. We are adults. Act accordingly. > > > > Don't be confused. I also thought the m

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Warner Losh
On Wed, Sep 2, 2020 at 12:46 PM Dan Langille wrote: > On Wed, Sep 2, 2020, at 2:36 PM, Ian Lepore wrote: > > > Seriously, Warner? > > Yes, seriously. We are adults. Act accordingly. > I agree it was over the top. > Don't be confused. I also thought the message he was replying to was out > of

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Ian Lepore
On Wed, 2020-09-02 at 14:45 -0400, Dan Langille wrote: > On Wed, Sep 2, 2020, at 2:36 PM, Ian Lepore wrote: > > > Seriously, Warner? > > Yes, seriously. We are adults. Act accordingly. > > Don't be confused. I also thought the message he was replying to was out of > line. > > > I applaud Stev

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Warner Losh
On Wed, Sep 2, 2020 at 12:36 PM Ian Lepore wrote: > On Wed, 2020-09-02 at 11:11 -0600, Warner Losh wrote: > > On Wed, Sep 2, 2020 at 10:47 AM Steve Kargl < > > s...@troutmask.apl.washington.edu> wrote: > > > > > On Wed, Sep 02, 2020 at 12:14:08PM -0400, Ed Maste wrote: > > > > On Wed, 2 Sep 2020

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Dan Langille
On Wed, Sep 2, 2020, at 2:36 PM, Ian Lepore wrote: > Seriously, Warner? Yes, seriously. We are adults. Act accordingly. Don't be confused. I also thought the message he was replying to was out of line. > I applaud Steve's message as being the first one in this thread that > has any real value

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Steve Kargl
On Wed, Sep 02, 2020 at 11:11:50AM -0600, Warner Losh wrote: > On Wed, Sep 2, 2020 at 10:47 AM Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > This is an insultingly stupid comment to make. We don't need people to say > the obvious. > > This sort of comment isn't helpful. People wil

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Ian Lepore
On Wed, 2020-09-02 at 11:11 -0600, Warner Losh wrote: > On Wed, Sep 2, 2020 at 10:47 AM Steve Kargl < > s...@troutmask.apl.washington.edu> wrote: > > > On Wed, Sep 02, 2020 at 12:14:08PM -0400, Ed Maste wrote: > > > On Wed, 2 Sep 2020 at 02:31, Steve Kargl > > > wrote: > > > > > > > > > A short

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Theron
On 2020-09-02 12:47, Steve Kargl wrote: Checking out /usr/src as u...@freebsd.org svn checkout svn+ssh://u...@svn.freebsd.org/base/head /usr/src git ... Checking out /usr/src without freebsd.org account svn checkout https://svn.freebsd.org/base/head ${HOME}/freebsd/src git ...

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Warner Losh
On Wed, Sep 2, 2020 at 10:47 AM Steve Kargl < s...@troutmask.apl.washington.edu> wrote: > On Wed, Sep 02, 2020 at 12:14:08PM -0400, Ed Maste wrote: > > On Wed, 2 Sep 2020 at 02:31, Steve Kargl > > wrote: > > > > > > > A short intro on git for svn users: > > > > https://hackmd.io/ML5TSl8mQ5-27B5eq

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Steve Kargl
On Wed, Sep 02, 2020 at 12:14:08PM -0400, Ed Maste wrote: > On Wed, 2 Sep 2020 at 02:31, Steve Kargl > wrote: > > > > > A short intro on git for svn users: > > > https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view > > > > > > > ROTFL. From the "short intro", 2nd sentence. > > > > New committers are ass

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Warner Losh
> On Sep 2, 2020, at 10:14 AM, Ed Maste wrote: > > On Wed, 2 Sep 2020 at 02:31, Steve Kargl > wrote: >> >>> A short intro on git for svn users: >>> https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view >>> >> >> ROTFL. From the "short intro", 2nd sentence. >> >> New committers are assumed to alr

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Warner Losh
> On Sep 1, 2020, at 10:59 PM, Greg 'groggy' Lehey wrote: > > On Tuesday, 1 September 2020 at 13:14:10 -0400, Ed Maste wrote: >> We've been updating the svn-git converter and pushing out a new >> converted repo every two weeks, and are now approaching the time where >> we'd like to commit to t

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Dimitry Andric
On 2 Sep 2020, at 17:18, Ed Maste wrote: > > On Wed, 2 Sep 2020 at 07:51, Mathieu Arnold wrote: >> >>> Git also supports sha-256 soon now, adoption should >>> be researched from various online article series and >>> work product before committing plans... >>> https://lwn.net/Articles/823352/ >>

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Ed Maste
On Wed, 2 Sep 2020 at 02:31, Steve Kargl wrote: > > > A short intro on git for svn users: > > https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view > > > > ROTFL. From the "short intro", 2nd sentence. > > New committers are assumed to already be familiar with the basic > operation of Git. If not, start

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Ed Maste
On Wed, 2 Sep 2020 at 07:51, Mathieu Arnold wrote: > > > Git also supports sha-256 soon now, adoption should > > be researched from various online article series and > > work product before committing plans... > > https://lwn.net/Articles/823352/ > > https://git-scm.com/docs/hash-function-transiti

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-02 Thread Mathieu Arnold
On Wed, Sep 02, 2020 at 01:20:22AM -0400, grarpamp wrote: > The underlying initializing 'git init' commit hash must be > signed by security officer key having sufficient human PGP-WoT. > > Git also supports sha-256 soon now, adoption should > be researched from various online article series and >

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-01 Thread Steve Kargl
On Wed, Sep 02, 2020 at 08:01:17AM +0200, Kurt Jaeger wrote: > Hi! > > > On Tuesday, 1 September 2020 at 13:14:10 -0400, Ed Maste wrote: > > > We've been updating the svn-git converter and pushing out a new > > > converted repo every two weeks, and are now approaching the time where > > > we'd li

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-01 Thread Kurt Jaeger
Hi! > On Tuesday, 1 September 2020 at 13:14:10 -0400, Ed Maste wrote: > > We've been updating the svn-git converter and pushing out a new > > converted repo every two weeks, and are now approaching the time where > > we'd like to commit to the tree generated by the exporter, > > ... > > Somehow

Re: Plans for git (was: Please check the current beta git conversions)

2020-09-01 Thread grarpamp
The underlying initializing 'git init' commit hash must be signed by security officer key having sufficient human PGP-WoT. Git also supports sha-256 soon now, adoption should be researched from various online article series and work product before committing plans... https://lwn.net/Articles/82335

Plans for git (was: Please check the current beta git conversions)

2020-09-01 Thread Greg 'groggy' Lehey
On Tuesday, 1 September 2020 at 13:14:10 -0400, Ed Maste wrote: > We've been updating the svn-git converter and pushing out a new > converted repo every two weeks, and are now approaching the time where > we'd like to commit to the tree generated by the exporter, > ... Somehow I've missed this de