Ulrich Spörlein wrote in
:
|On Mon, Oct 5, 2020 at 7:21 PM Steffen Nurpmeso wrote:
|> Ulrich Spörlein wrote in
|> :
|>|On Sun, Oct 4, 2020 at 1:53 AM Bakul Shah wrote:
|>|> git clone --bare https://cgit-beta.freebsd.org/src.git
|>|> cd src.git
|>|> git fetch origin 'refs/notes/*:refs/not
On Mon, Oct 5, 2020 at 7:21 PM Steffen Nurpmeso wrote:
> Ulrich Spörlein wrote in
> :
> |On Sun, Oct 4, 2020 at 1:53 AM Bakul Shah wrote:
> |> git clone --bare https://cgit-beta.freebsd.org/src.git
> |> cd src.git
> |> git fetch origin 'refs/notes/*:refs/notes/origin/*' # <<< not sure
> abo
Ulrich Spörlein wrote in
:
|On Sun, Oct 4, 2020 at 1:53 AM Bakul Shah wrote:
|> git clone --bare https://cgit-beta.freebsd.org/src.git
|> cd src.git
|> git fetch origin 'refs/notes/*:refs/notes/origin/*' # <<< not sure about
|> this
|> # don't recall if I manually added the seco
Hello.
Bakul Shah wrote in
:
|On Oct 3, 2020, at 3:14 PM, Steffen Nurpmeso wrote:
|> And still "git fetch" fails with
|>
|> POST git-upload-pack (chunked)
|> error: RPC failed; curl 55 OpenSSL SSL_write: Broken pipe, errno 32
|> fatal: the remote end hung up unexpectedly
|>
|> My co
On Sun, Oct 4, 2020 at 1:53 AM Bakul Shah wrote:
> FWIW, I have a bare repo with the following config file
>
> [core]
> repositoryformatversion = 0
> filemode = true
> bare = true
> logallrefupdates = true
> [remote "origin"]
> url = https://cgit-beta.freeb
On Oct 3, 2020, at 3:14 PM, Steffen Nurpmeso wrote:
>
> And still "git fetch" fails with
>
> POST git-upload-pack (chunked)
> error: RPC failed; curl 55 OpenSSL SSL_write: Broken pipe, errno 32
> fatal: the remote end hung up unexpectedly
>
> My config file is
>
> [core]
>repositoryfor
...
Steffen Nurpmeso wrote in
...
> I tried simply updating my github clone by switching
>
>url = https://cgit-beta.freebsd.org/src.git
>#url = https://github.com/freebsd/freebsd.git
...
|It fails again, repeatedly [.]
|
| POST git-upload-pack (chunked)
| error:
Steffen Nurpmeso wrote in
<20200903191410.sgjuq%stef...@sdaoden.eu>:
|For one: thanks all, it now works!
|
|Steffen Nurpmeso wrote in
| <20200903151825.g_rv9%stef...@sdaoden.eu>:
||Renato Botelho wrote in
|| :
|||On 02/09/20 20:20, Steffen Nurpmeso wrote:
|||> Ed Maste wrote in
|||> :
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
For one: thanks all, it now works!
Steffen Nurpmeso wrote in
<20200903151825.g_rv9%stef...@sdaoden.eu>:
|Renato Botelho wrote in
| :
||On 02/09/20 20:20, Steffen Nurpmeso wrote:
||> Ed Maste wrote in
||> :
||>
||> I tried simply updating my github clone by switching
||>
||>url =
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
>
>
> > 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
Renato Botelho wrote in
:
|On 02/09/20 20:20, Steffen Nurpmeso wrote:
|> Ed Maste wrote in
|> :
|>
|> I tried simply updating my github clone by switching
|>
|>url = https://cgit-beta.freebsd.org/src.git
|>#url = https://github.com/freebsd/freebsd.git
|>
|> and whereas ls-re
On 2020-09-03 10:05, Steve Wills wrote:
> Hi,
>
> On 9/1/20 1:14 PM, 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, and
>> gua
Hi,
On 9/1/20 1:14 PM, 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, and
guarantee that hashes will remain consistent from this poin
On Thu, Sep 03, 2020 at 08:48:59AM -0300, Renato Botelho wrote:
> On 02/09/20 20:20, Steffen Nurpmeso wrote:
> > Ed Maste wrote in
> > :
> >
> > I tried simply updating my github clone by switching
> >
> >url = https://cgit-beta.freebsd.org/src.git
> >#url = https://github.com/freebsd/f
On 02/09/20 20:20, Steffen Nurpmeso wrote:
Ed Maste wrote in
:
I tried simply updating my github clone by switching
url = https://cgit-beta.freebsd.org/src.git
#url = https://github.com/freebsd/freebsd.git
and whereas ls-remote worked fine fetch -v --dry-run aborted as
well as normal f
> 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
On 9/1/20, Shawn Webb wrote:
> I'm curious if there's any plans for read-only access over ssh.
> Trusting FreeBSD's ssh key material is likely easier than trusting
> HTTPS in certain regions.
A bit moot when such key materials of all services, and repos,
and ticketing, and reviews, and builds, an
Ed Maste wrote in
:
I tried simply updating my github clone by switching
url = https://cgit-beta.freebsd.org/src.git
#url = https://github.com/freebsd/freebsd.git
and whereas ls-remote worked fine fetch -v --dry-run aborted as
well as normal fetch, after dumping dozens of POSTs
POST git-
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
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
On Wed, Sep 02, 2020 at 08:30:28AM +, Thomas Mueller wrote:
> NetBSD plans to switch from cvs to Mercurial.
So ... from square wheels, to triangular ones???
mcl
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/
> 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
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
On Wed, 2020-09-02 at 15:16:38 +0200, Olivier Certner wrote:
> Hi,
>
> > > 2.5 GB in .git directory sounds crazy and incomprehensible to me.
> >
> > 2.5GB is for the full history, if you only care about the main branch,
> > you can clone with:
> >
> > (snip)
>
> I do not reproduce this, but ins
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.
> >
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
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
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
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
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
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
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
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 ...
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
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
On Tue, 1 Sep 2020 at 22:38, Thomas Mueller wrote:
>
> from Ed Maste:
>
> > > Any guidance on amount of diskspace and how long it takes to clone the
> > > repo ?
>
> > I see just over 3GB in my clone, including about 2.5GB in the .git
> > directory.
In fact my clone was larger than it should be
> 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
> 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
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/
>>
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
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
> Receiving objects: 100% (3763254/3763254), 1.10 GiB | 876.00 KiB/s, done.
> Executed in 30.36 mins
Experienced a comparable full clone time yesterday afternoon from
France (did not precisely `time` it). The bandwidth oscillated between 600 and
1.2MiB/s steadily during the transfer. T
Hi,
> > 2.5 GB in .git directory sounds crazy and incomprehensible to me.
>
> 2.5GB is for the full history, if you only care about the main branch,
> you can clone with:
>
> (snip)
I do not reproduce this, but instead see `du` reporting 1.2GiB just after a
simple clone (no options), which AFA
On Wed, Sep 02, 2020 at 02:37:45AM +, Thomas Mueller wrote:
> from Ed Maste:
>
> > > Any guidance on amount of diskspace and how long it takes to clone the
> > > repo ?
>
> > I see just over 3GB in my clone, including about 2.5GB in the .git
> > directory.
>
> > If you have only one checko
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
>
On Wed, 02 Sep 2020 08:30:28 +
"Thomas Mueller" wrote:
> from Kevin Oberman:
>
> > > So I am abandoning FreeBSD 12.x .
>
> > > Hopefully I could update 13-current from within 13-current where I have no
> > > internet access but could use git from NetBSD, where I also have svn.
>
from Kevin Oberman:
> > So I am abandoning FreeBSD 12.x .
> > Hopefully I could update 13-current from within 13-current where I have no
> > internet access but could use git from NetBSD, where I also have svn.
> > Tom
> Not really much different from subversion. .svn in /usr/sys is a
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
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
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
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
On Tue, Sep 1, 2020 at 7:38 PM Thomas Mueller wrote:
> from Ed Maste:
>
> > > Any guidance on amount of diskspace and how long it takes to clone the
> repo ?
>
> > I see just over 3GB in my clone, including about 2.5GB in the .git
> directory.
>
> > If you have only one checkout git will require
from Ed Maste:
> > Any guidance on amount of diskspace and how long it takes to clone the repo
> > ?
> I see just over 3GB in my clone, including about 2.5GB in the .git directory.
> If you have only one checkout git will require a bit more disk space
> than svn. However, if you have two or mor
On Tue, Sep 01, 2020 at 01:43:19PM -0400, Ed Maste wrote:
> Thanks for the report - I wouldn't be surprised if the host is a bit
> bogged down from folks trying this just after my message went out.
> Once your clone finishes please do let us know how long it took
> overall.
time git clone https://
On Tue, Sep 01, 2020 at 01:14:10PM -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, and
> guarantee that hashes will remain c
On Tue, 1 Sep 2020 at 13:37, Poul-Henning Kamp wrote:
>
>
> Goran Mekić writes:
>
> > While I can clone src nicely, it is very slow in Serbia/Europe. The best
> > speed I got is 1.45MB/s but it's mostly around 700kB/s (still cloning).
>
> I was about to ask about that:
>
> Any guidance on
On Tue, 1 Sep 2020 at 13:23, Goran Mekić wrote:
>
> Hello,
>
> While I can clone src nicely, it is very slow in Serbia/Europe.
Thanks for the report - I wouldn't be surprised if the host is a bit
bogged down from folks trying this just after my message went out.
Once your clone finishes please do
On Tue, Sep 01, 2020 at 01:14:10PM -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, and
> guarantee that hashes will remain c
Goran Mekić writes:
> While I can clone src nicely, it is very slow in Serbia/Europe. The best
> speed I got is 1.45MB/s but it's mostly around 700kB/s (still cloning).
I was about to ask about that:
Any guidance on amount of diskspace and how long it takes to clone the repo ?
--
Po
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, and
guarantee that hashes will remain consistent from this point. At this
point the Git Working Group bel
62 matches
Mail list logo
