Re: Please check the current beta git conversions

[Steffen Nurpmeso]

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/notes/origin/*' # <<< not sure
 ...
 |>|This is a quirk of the conversion. We have to patch up several tags
 |>|post-conversion, which patches up their notes, but that happens after the
 |>|full conversion is done. Notes are just 1 long linear branch, which ...
 |>|well, is unfortunate. So essentially every update to the repo changes the
 |>|last couple hundred of hashes for the commit notes
 ...
 |>|This will all cease with the final transition, obviously.
 |>
 |> I guess they will simply vanish and i could remove the reference
 |> from my config already today?
 |>
 |They will not vanish. They are there to map git commits back to SVN
 |revisions.
 |What will change is that they'll never change again and are just a static,
 |eternal record
 |of that mapping.
 |
 |Of course, freebsd committers can then in the future push their own notes
 |(but not force-push them) , but it's not clear what you would want to put
 |into them?
 |
 |If you don't have a need to ever map git <-> svn commits, then you don't
 |need to fetch
 |them indeed.

Fantastic!  Sure thing if FreeBSD moves over to git as such.
Thank you.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Ulrich Spörlein]

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
> about
>  |> this
>  |> # don't recall if I manually added the second fetch line in the
>  |> config file.
>  |> # but notes get fetched fine; though I don't understand why \
>  |> 100MB+
>  |> get
>  |> # downloaded every time even though only a few files change.
>  |
>  |This is a quirk of the conversion. We have to patch up several tags
>  |post-conversion, which patches up their notes, but that happens after the
>  |full conversion is done. Notes are just 1 long linear branch, which ...
>  |well, is unfortunate. So essentially every update to the repo changes the
>  |last couple hundred of hashes for the commit notes
> objects/tree/DAG/linear
>  |train. They always need to get force-pushed upstream and you always have
> to
>  |re-fetch quite a bunch of them.
>
> I was astonished to see third-to-last commit on my notes is from
> Dag-Erling Smørgrav "+svn path=/vendor-crypto/openssh/5.8p2/;
> revision=221485; tag=vendor/openssh/5.8p2".
>
>  |This will all cease with the final transition, obviously.
>
> I guess they will simply vanish and i could remove the reference
> from my config already today?
>
>
They will not vanish. They are there to map git commits back to SVN
revisions.
What will change is that they'll never change again and are just a static,
eternal record
of that mapping.

Of course, freebsd committers can then in the future push their own notes
(but not force-push them) , but it's not clear what you would want to put
into them?

If you don't have a need to ever map git <-> svn commits, then you don't
need to fetch
them indeed.

hth
Uli
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Steffen Nurpmeso]

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 second fetch line in the
 |> config file.
 |> # but notes get fetched fine; though I don't understand why \
 |> 100MB+
 |> get
 |> # downloaded every time even though only a few files change.
 |
 |This is a quirk of the conversion. We have to patch up several tags
 |post-conversion, which patches up their notes, but that happens after the
 |full conversion is done. Notes are just 1 long linear branch, which ...
 |well, is unfortunate. So essentially every update to the repo changes the
 |last couple hundred of hashes for the commit notes objects/tree/DAG/linear
 |train. They always need to get force-pushed upstream and you always have to
 |re-fetch quite a bunch of them.

I was astonished to see third-to-last commit on my notes is from
Dag-Erling Smørgrav "+svn path=/vendor-crypto/openssh/5.8p2/;
revision=221485; tag=vendor/openssh/5.8p2".

 |This will all cease with the final transition, obviously.

I guess they will simply vanish and i could remove the reference
from my config already today?

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Steffen Nurpmeso]

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 config file is
 |> 
 |>  [core]
 |>repositoryformatversion = 0
 |>filemode = true
 |>bare = false
 |>logallrefupdates = true
 |>  [remote "origin"]
 |>url = https://cgit-beta.freebsd.org/src.git
 |>#url = https://github.com/freebsd/freebsd.git
 |>fetch = +refs/heads/releng/5.5:refs/remotes/origin/releng/5.5
 |>fetch = +refs/heads/releng/6.4:refs/remotes/origin/releng/6.4
 |>fetch = +refs/heads/releng/7.4:refs/remotes/origin/releng/7.4
 |>fetch = +refs/heads/releng/8.4:refs/remotes/origin/releng/8.4
 |>fetch = +refs/heads/releng/9.3:refs/remotes/origin/releng/9.3
 |>fetch = +refs/heads/releng/10.3:refs/remotes/origin/releng/10.4
 |>fetch = +refs/heads/releng/11.4:refs/remotes/origin/releng/11.4
 |>fetch = +refs/heads/releng/12.1:refs/remotes/origin/releng/12.1
 |>fetch = +refs/heads/stable/12:refs/remotes/origin/stable/12
 |>fetch = +refs/heads/main:refs/remotes/origin/main
 |>fetch = +refs/notes/*:refs/notes/*
 |
 |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.freebsd.org/src.git
 | fetch = +refs/heads/*:refs/remotes/origin/*
 | fetch = +refs/notes/*:refs/notes/*
 |[branch "main"]
 | remote = origin
 | merge = refs/heads/main
 |
 |/usr/src is a worktree and everything seems to be working fine.
 |
 |I manually converted to a bare repo (first testing this with a much
 |smaller repo) and fixed up various refs. But probably safer to
 |just start from scratch:
 |
 |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 second fetch line in the config \
 | file.
 | # but notes get fetched fine; though I don't understand why 100MB+ get
 | # downloaded every time even though only a few files change.
 |
 |git worktree add  main
 |git worktree add  stable/12

Interesting new way to work with external check out directories,
i only knew about the environment variable approach.  (Though have
forgotten the details, i am using less of git than what mankind
does with its brain.)
I use bare repositories only for the git repositories i publish in
the web (i have the very same thing locally 1:1 and the
post-receive hook then forwards).
This old habit of mine (an arena-manager-null branch without
files) is maybe strange.  The monthly update still updates all
repos, merges, garbage collects and then checks out this branch in
order to create the backup without any checkout.  Except for some
bootstrap things, like git itself.  It was meant for minimal
backup sizes while still being able to bootstrap in the nowhere
without internet accesss.  I never used that.  Hm.

Sure, after the lengthy matching of objects failed i was about to
simply refetch the entire repository, but i only had ~800 MB
download left, so i had to interrupt that.
I was just reporting because i thought an automated updater should
work instead of failing as above.  It must be some limit on the
server, runtime or whatever, which causes the common history
search to be aborted.  Maybe it does not abort for you because you
have a tremendously potent internet connection, whereas with this
wifi thing you always have to take into account tenths of seconds
(i would say) delay whenever a new chunk comes in after some
delay.  Maybe it is this.

Anyhow, it seems for now it would be better for me to either wait
until -beta becomes stable or switch back to the github version
until then.  I should not have thrown that thing away, 1.4+ GB of
data, that is ugly.  And all the stuff is so badly packed, on
Saturday i then cloned wolfssl out of interest and had to download
179 or so MB from github for [master] which after packing ended up
as not more than 39 MB.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Ulrich Spörlein]

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.freebsd.org/src.git
> fetch = +refs/heads/*:refs/remotes/origin/*
> fetch = +refs/notes/*:refs/notes/*
> [branch "main"]
> remote = origin
> merge = refs/heads/main
>
> /usr/src is a worktree and everything seems to be working fine.
>
> I manually converted to a bare repo (first testing this with a much
> smaller repo) and fixed up various refs. But probably safer to
> just start from scratch:
>
> 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 second fetch line in the
> config file.
> # but notes get fetched fine; though I don't understand why 100MB+
> get
> # downloaded every time even though only a few files change.
>

This is a quirk of the conversion. We have to patch up several tags
post-conversion, which patches up their notes, but that happens after the
full conversion is done. Notes are just 1 long linear branch, which ...
well, is unfortunate. So essentially every update to the repo changes the
last couple hundred of hashes for the commit notes objects/tree/DAG/linear
train. They always need to get force-pushed upstream and you always have to
re-fetch quite a bunch of them.

This will all cease with the final transition, obviously.

hth
Uli
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Bakul Shah]

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]
>repositoryformatversion = 0
>filemode = true
>bare = false
>logallrefupdates = true
>  [remote "origin"]
>url = https://cgit-beta.freebsd.org/src.git
>#url = https://github.com/freebsd/freebsd.git
>fetch = +refs/heads/releng/5.5:refs/remotes/origin/releng/5.5
>fetch = +refs/heads/releng/6.4:refs/remotes/origin/releng/6.4
>fetch = +refs/heads/releng/7.4:refs/remotes/origin/releng/7.4
>fetch = +refs/heads/releng/8.4:refs/remotes/origin/releng/8.4
>fetch = +refs/heads/releng/9.3:refs/remotes/origin/releng/9.3
>fetch = +refs/heads/releng/10.3:refs/remotes/origin/releng/10.4
>fetch = +refs/heads/releng/11.4:refs/remotes/origin/releng/11.4
>fetch = +refs/heads/releng/12.1:refs/remotes/origin/releng/12.1
>fetch = +refs/heads/stable/12:refs/remotes/origin/stable/12
>fetch = +refs/heads/main:refs/remotes/origin/main
>fetch = +refs/notes/*:refs/notes/*

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.freebsd.org/src.git
fetch = +refs/heads/*:refs/remotes/origin/*
fetch = +refs/notes/*:refs/notes/*
[branch "main"]
remote = origin
merge = refs/heads/main

/usr/src is a worktree and everything seems to be working fine.

I manually converted to a bare repo (first testing this with a much
smaller repo) and fixed up various refs. But probably safer to
just start from scratch:

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 second fetch line in the config 
file.
# but notes get fetched fine; though I don't understand why 100MB+ get
# downloaded every time even though only a few files change.

git worktree add  main
git worktree add  stable/12

etc.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Steffen Nurpmeso]

...
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: RPC failed; curl 18 transfer closed with outstanding read \
 |  data remaining
 |  fatal: the remote end hung up unexpectedly

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]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
  [remote "origin"]
url = https://cgit-beta.freebsd.org/src.git
#url = https://github.com/freebsd/freebsd.git
fetch = +refs/heads/releng/5.5:refs/remotes/origin/releng/5.5
fetch = +refs/heads/releng/6.4:refs/remotes/origin/releng/6.4
fetch = +refs/heads/releng/7.4:refs/remotes/origin/releng/7.4
fetch = +refs/heads/releng/8.4:refs/remotes/origin/releng/8.4
fetch = +refs/heads/releng/9.3:refs/remotes/origin/releng/9.3
fetch = +refs/heads/releng/10.3:refs/remotes/origin/releng/10.4
fetch = +refs/heads/releng/11.4:refs/remotes/origin/releng/11.4
fetch = +refs/heads/releng/12.1:refs/remotes/origin/releng/12.1
fetch = +refs/heads/stable/12:refs/remotes/origin/stable/12
fetch = +refs/heads/main:refs/remotes/origin/main
fetch = +refs/notes/*:refs/notes/*

And i am somewhat behind due to the update failures (not that it
matters, of course)

  #?141|kent:free-src.git$ git sr
  d7ad7208f47d37aae16d55f5dcb743b25dcd0288 refs/heads/arena-manager-null
  ef7e23176ea6dcda108f4e19b9c1852b7fa5fb55 refs/notes/commits
  88fc88f775381ab664fc2ca52ab143b94315743d refs/remotes/origin/main
  c032bc8ca5d4618ad349a53392fd692afef9fe4e refs/remotes/origin/releng/10.4
  24e863807ab509af9c38e84b4e5df34ff4fdf9e2 refs/remotes/origin/releng/11.2
  889f726543f5202c54ad14b81d5d16a85379ffe5 refs/remotes/origin/releng/11.4
  6fb517db6dea0333c4b0bef3098abb87656a6d34 refs/remotes/origin/releng/12.1
  101374bc1b346a37aa46393599b0969a03c8ca46 refs/remotes/origin/releng/5.5
  385a94b8751c71f178bba86c13f083895dbe006d refs/remotes/origin/releng/6.4
  f864cd1bca002396fa92715878379bc2fdad8af0 refs/remotes/origin/releng/7.4
  b4323ad1fd9f310a36e595a031d77fe0f0e38472 refs/remotes/origin/releng/8.4
  6845fb3a03394a42484e36d5f9e07e0cf14fec0d refs/remotes/origin/releng/9.3
  ae4ea149fd21ae30fb0faa7104f5e4ee51e3147c refs/remotes/origin/stable/11
  6a26cffb54271f343520a1731cf5c8f2c909194b refs/remotes/origin/stable/12
  77a8b861086dccc41c08ce7d0c795a0bd2f7a1fb refs/tags/release/10.3.0
  6025619ef8af561f9d8f3dff13c7802a1d447b7a refs/tags/release/11.4.0
  4b3b0f6c1e9d013d6cff6dfd9459f5dc4d9ece08 refs/tags/release/12.1.0
  2326bdbbcad4640f22d387060c7d3b363fff3b39 refs/tags/release/5.5.0
  b9083afc65e8ac36f65d52d7859d31a11da05aef refs/tags/release/6.4.0
  c6788c2a1bd371b64a299c6f98fe753f9a610de2 refs/tags/release/7.4.0
  acbed3693070aed8e250cd993b4d4975dd12efb1 refs/tags/release/8.1.0
  98566c7da1c45611953885e902507c562388660b refs/tags/release/8.4.0
  87d65461806585dcf89d3c80f46135117a055140 refs/tags/release/9.3.0
  #?0|kent:free-src.git$ git log -1 origin/main
  commit 88fc88f775381ab664fc2ca52ab143b94315743d (refs/remotes/origin/main)
  Author: Andrew Turner 
  AuthorDate: 2020-09-03 10:11:12 +
  Commit: Andrew Turner 
  CommitDate: 2020-09-03 10:11:12 +

  Switch to an empty ttbr0 pagetable when the MMU is enabled

  We don't need these pagetables after the early boot. Remove the chance we
  write to memory we didn't expect to and remove architectural undefined
  behaviour.

  Reviewed by:alc (earlier version), mmel
  Sponsored by:   Innovate UK
  Differential Revision:  https://reviews.freebsd.org/D22606

  Notes:
  svn path=/head/; revision=365296

Somewhat eagerly waiting for cgit-beta. becoming cgit.,

Thanks and an affordable Sunday and (uff)
Ciao, 

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Steffen Nurpmeso]

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
 |||>   :
 |||> 
 |||> 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-upload-pack (gzip 1472 to 804 bytes)
 |||>...
 |||>POST git-upload-pack (gzip 976722 to 483608 bytes)
 |||>POST git-upload-pack (chunked)
 |||>error: RPC failed; HTTP 413 curl 22 The requested URL returned \
 |||>error: 413
 |||>fatal: the remote end hung up unexpectedly
 ...

It fails again, repeatedly and reproducably for my monthly update.

  POST git-upload-pack (chunked)
  error: RPC failed; curl 18 transfer closed with outstanding read data 
remaining
  fatal: the remote end hung up unexpectedly

A nice Sunday from Germany i wish.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 standard I try to set for myself: so
it was doubly wrong. I've been doing it a lot this year, guess I'm not
coping as well as I thought with the times. It's no excuse, though, and I'm
sorry.

I felt bad about over-reacting so I came back to things fresh today. On
fresh reading, your suggestions are good ones. Very similar to the ones I
came to after spending some quality time trying to edit the document you'd
offered the suggestion to. The content and focus isn't quite right there. I
spent a couple hours trying to fix it, only to find myself in a dead end I
couldn't puzzle my way out of before quitting for the day... I'll give it
another try over the weekend or next week.

So please accept my apology for being a jerk, yelling at you in a truly
unprofessional way and screaming when I should really have been listening.
Again, anything I say by way of explanation doesn't justify it at all.

Warner

On Wed, Sep 2, 2020 at 11:11 AM 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 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 by reading the Git Book.
>> >
>> > This doc started as a direct translation of the Subversion primer,
>> > which has as its first sentence:
>> > > New committers are assumed to already be familiar with the basic
>> operation of Subversion. If not, start by reading the Subversion Book.
>> >
>> > As with the Subversion primer the doc is intended to provide a quick
>> > reference for day-to-day commands, but not act as a reference or
>> > introduction to the entire theory of operation of the associated VCS.
>>
>> Like GCC, which did the svn to git dance at start of the year,
>> FreeBSD is throwing away a decade+ of corporate knowledge of
>> working with svn and /usr/src.  What is needed is a succinct
>> translation of the most common svn commands translated to git.
>>
>> 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 ...
>>
>> Creating diff against updated head.
>>
>>   svn update
>>   svn diff > patch.diff
>>
>>   git ...
>>
>> Adding a new file
>>
>>   svn add /usr/src/libm/msun/src/_s_sinpi.c
>>
>>   git ...
>>
>> Committing a change to /usr/src
>>
>>   svn update
>>   svn diff  | more (everyone does one last check, right?)
>>   svn commit 
>>
>>   git ...
>>
>
> 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 will just ignore you if you
> make too many of them like it.
>
> Warner
>
>
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Steffen Nurpmeso]

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 = 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-upload-pack (gzip 1472 to 804 bytes)
 ||>...
 ||>POST git-upload-pack (gzip 976722 to 483608 bytes)
 ||>POST git-upload-pack (chunked)
 ||>error: RPC failed; HTTP 413 curl 22 The requested URL returned \
 ||>error: 413
 ||>fatal: the remote end hung up unexpectedly
 ||> 
 ||> Maybe clone from scratch instead, but mysterious it is?
 ||> Good night, and Ciao from Germany,
 ||
 ||github and cgit-beta repositories are not the same.  Commit hashes won't 
 ||match so you cannot simply change the URL.
 |
 |Yes i know that, but most of the blobs are of course the same, no?

Having said that, i switched to git in i think 2011 and never ever
read anything about the protocol or almost anything else ever
since ...  Except that rev-parse changed its output order which
broke a (primitive) script (git-topic-creator) of mine, but that
was in 2013.

So: it may well be that git does not really take care for finding
local data blobs unless there are commits with shared ancestors or
what (the two repositories anyway show up as "warning: no common
commits").  Let's see where this ends...

That reminds me of the fossil/venti storage system of Plan9, with
the short-time local cache and the hash-based backing store, which
just stores digested blocks.  There was a graphic which showed how
data consumption exploded at the beginning, but the curve went
flatter and flatter, and it was explicitly noted that the masses
of people in Bell Labs did a lot with multimedia, videos and such.
Which i found surprising.

Old github pack
  -r--r- 1 steffen code 1526603739 Aug  2 01:47 
pack-92bcd61e50e1a09e27e8aa4a67e0878468f01f79.pack
  -r--r- 1 steffen code  136779336 Aug  2 01:47 
pack-92bcd61e50e1a09e27e8aa4a67e0878468f01f79.idx

  warning: no common commits
  remote: Enumerating objects: 920487, done.
  remote: Counting objects: 100% (920487/920487), done.
  remote: Compressing objects: 100% (254705/254705), done.
  remote: Total 4909613 (delta 876272), reused 665791 (delta 665782), 
pack-reused 3989126
  Receiving objects: 100% (4909613/4909613), 1.25 GiB | 396.00 KiB/s, done.

Hm.  It definetely must have downloaded masses of duplicate data.
I must admit, the largest repo which had to be updated very often
(despite the borked NetBSD thing on github, years ago) was
ghostscript.  There i looked, but find it quite different, if
i recall correctly.  I did not blame git for the mess there.

  Resolving deltas: 100% (3429285/3429285), done.
  From https://cgit-beta.freebsd.org/src
   + 606d234876ce...101374bc1b34 releng/5.5 -> origin/releng/5.5  
(forced update)
   + 2132c100d27f...385a94b8751c releng/6.4 -> origin/releng/6.4  
(forced update)
   + c462a28e0cae...f864cd1bca00 releng/7.4 -> origin/releng/7.4  
(forced update)
   + 3ffe9881628f...b4323ad1fd9f releng/8.4 -> origin/releng/8.4  
(forced update)
   + 34073209c9c9...6845fb3a0339 releng/9.3 -> origin/releng/9.3  
(forced update)
   + 57fbb64699be...c032bc8ca5d4 releng/10.3-> origin/releng/10.4  
(forced update)
   + da2894488950...889f726543f5 releng/11.4-> origin/releng/11.4  
(forced update)
   + e1a11e350964...6fb517db6dea releng/12.1-> origin/releng/12.1  
(forced update)
   + a9ff142f7dcc...6a26cffb5427 stable/12  -> origin/stable/12  
(forced update)
   + c660a28c68a8...88fc88f77538 main   -> origin/main  (forced 
update)

A masterpiece!

   + 16be7204f705...ef7e23176ea6 refs/notes/commits -> refs/notes/commits  
(forced update)
   * [new tag]   release/10.3.0 -> release/10.3.0
   * [new tag]   release/11.4.0 -> release/11.4.0
   * [new tag]   release/12.1.0 -> release/12.1.0
   * [new tag]   release/5.5.0  -> release/5.5.0
   * [new tag]   release/6.4.0  -> release/6.4.0
   * [new tag]   release/7.4.0  -> release/7.4.0
   * [new tag]   release/8.1.0  -> release/8.1.0
   - [new tag]   release/8.4.0  -> release/8.4.0
   - [new tag]   release/9.3.0  -> release/9.3.0

  -r--r- 1 steffen code 1344409784 Sep  3 20:44 
pack-0f656d44c6c8301d98ee51b69c3aacd8db9255ac.pack
  -r--r- 1 steffen code  137470236 Sep  3 20:44 
pack-0f656d44c6c8301d98ee51b69c3aacd8db9255ac.idx

I then garbage collected aggressively and pruned the two into

  -r--r- 1 steffen 

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

[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 git git and we being heading
> to this for 5 years"

Five years ago "all of my friends say that" was given as a fact, when
it was actually an anecdote.  That was why people (including myself)
were opposed to it.

Last year FreeBSD took a user survey.  That contained data.  And AFAIK
that was the basis of the decision.

Plus, the industry had changed in the ensuing 4 years.

mcl
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 like to commit to the tree generated by the exporter,
> >> ...
> > 
> > Somehow I've missed this development.  Reading between the lines, it
> > seems that we're planning to move from svn to git, but I can't recall
> > seeing any announcement on the subject.  Can you give some background?
> > It would also be nice to find a HOWTO both for the migration and for
> > life with git.
> 
> We?ve been talking about the transition for about 5 years now. So far, only 
> people interested in git have showed up to do any work at all. Subversion has 
> lost, and even Apache, the main users of it, are moving to git. We started 
> early in the year with the firm plans and have been working on it since then. 
> These conversations have happened all over the place, and we?ve been posting 
> to developers for months now...

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 git git and we being heading
to this for 5 years"

Would you expect those opposed to this idea to help with it? Really?

> There?s some draft guides, but they need work which is on my plate. They are 
> OK, but have some issues on the more complicated bits.
> 
> Warner

-- 
Rod Grimes rgri...@freebsd.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Steffen Nurpmeso]

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-remote worked fine fetch -v --dry-run aborted as
 |> well as normal fetch, after dumping dozens of POSTs
 |> 
 |>POST git-upload-pack (gzip 1472 to 804 bytes)
 |>...
 |>POST git-upload-pack (gzip 976722 to 483608 bytes)
 |>POST git-upload-pack (chunked)
 |>error: RPC failed; HTTP 413 curl 22 The requested URL returned \
 |>error: 413
 |>fatal: the remote end hung up unexpectedly
 |> 
 |> Maybe clone from scratch instead, but mysterious it is?
 |> Good night, and Ciao from Germany,
 |
 |github and cgit-beta repositories are not the same.  Commit hashes won't 
 |match so you cannot simply change the URL.

Yes i know that, but most of the blobs are of course the same, no?
The same files.  All that is new are likely the notes and commit
objects, even the directory tree objects could often be the same,
but i do not know, also because i do not have the new data yet.
(But it is 100% that i will not actually inspect this deeply.)
Maybe they should split in cgit. and scm. (or .git) and use the
git-http-backend for clones on scm. (or .git) and then redirect
some requests, this works fine for years:

  url.redirect = (
 "^.*/([^/]+\.git/objects/.*)" => "https://???/scm/$1;,
 "^.*/([^/]+\.git/info/refs\?service.*)" =>
   "https:///scm/$1;
  )

I mean i really like saving some download that would go over
thousands of kilometres for absolutely nothing.
And i think it would be cool if all the many people which clone
the github repo just update to the finally landed freebsd.org
instance.

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Allan Jude]

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
>> guarantee that hashes will remain consistent from this point. At this
>> point the Git Working Group believes the conversion represents a
>> high-fidelity translation of the Subversion history, but would
>> appreciate additional review in case we've missed anything.
>>
>> I'd ask folks with an interest in the FreeBSD repository to clone the
>> beta conversion and review the converted history in the specific areas
>> they are interested in - e.g., specific contrib/ software, device
>> drivers, etc. This will also present our final opportunity to change
>> the author map file, if necessary.
>>
>> The beta src tree can be cloned via:
>> % git clone https://cgit-beta.freebsd.org/src.git freebsd-cgit-beta
>>
>> Please follow up this week if you notice any discrepancies or author
>> entries that require updates.
> 
> One issue that's been seen is adding this remote to an existing repo:
> 
> $ git remote add cgit-beta https://cgit-beta.freebsd.org/ports.git
> $ git fetch cgit-beta
> error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413
> fatal: the remote end hung up unexpectedly
> 
> 413 is Payload too large
> 
> This is because when you fetch, you're telling the other end what hashes
> you have and it's figuring out what to send you, and that list is too
> large, over 10m, I guess:
> 
> https://stackoverflow.com/questions/7489813/github-push-error-rpc-failed-result-22-http-code-413#15021750
> 
> 
> It's unclear if there's a way to tell the client to skip that and just
> fetch everything or if it's required to change the upload limit on the
> web server and if so how large would be appropriate/required.
> 
> Note fresh clone works fine.
> 
> Steve
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

I have raised the client_max_body_size setting on the web server that
serves the git repo, and people report it is working now. You might
still hit this error if you have a lot of unrelated histories in your
checkout, but, this should solve the issue for most people.

-- 
Allan Jude



signature.asc
Description: OpenPGP digital signature

Re: Please check the current beta git conversions

[Steve Wills]

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 point. At this
point the Git Working Group believes the conversion represents a
high-fidelity translation of the Subversion history, but would
appreciate additional review in case we've missed anything.

I'd ask folks with an interest in the FreeBSD repository to clone the
beta conversion and review the converted history in the specific areas
they are interested in - e.g., specific contrib/ software, device
drivers, etc. This will also present our final opportunity to change
the author map file, if necessary.

The beta src tree can be cloned via:
% git clone https://cgit-beta.freebsd.org/src.git freebsd-cgit-beta

Please follow up this week if you notice any discrepancies or author
entries that require updates.


One issue that's been seen is adding this remote to an existing repo:

$ git remote add cgit-beta https://cgit-beta.freebsd.org/ports.git
$ git fetch cgit-beta
error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413
fatal: the remote end hung up unexpectedly

413 is Payload too large

This is because when you fetch, you're telling the other end what hashes 
you have and it's figuring out what to send you, and that list is too 
large, over 10m, I guess:


https://stackoverflow.com/questions/7489813/github-push-error-rpc-failed-result-22-http-code-413#15021750

It's unclear if there's a way to tell the client to skip that and just 
fetch everything or if it's required to change the upload limit on the 
web server and if so how large would be appropriate/required.


Note fresh clone works fine.

Steve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Mathieu Arnold]

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/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-upload-pack (gzip 1472 to 804 bytes)
> >...
> >POST git-upload-pack (gzip 976722 to 483608 bytes)
> >POST git-upload-pack (chunked)
> >error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413
> >fatal: the remote end hung up unexpectedly
> > 
> > Maybe clone from scratch instead, but mysterious it is?
> > Good night, and Ciao from Germany,
> 
> github and cgit-beta repositories are not the same.  Commit hashes won't
> match so you cannot simply change the URL.

Right now, it is true, they differ, in the near future, when we switch,
the Github repository will be overwritten and they will be identical.

-- 
Mathieu Arnold


signature.asc
Description: PGP signature

Re: Please check the current beta git conversions

[Renato Botelho]

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 fetch, after dumping dozens of POSTs

   POST git-upload-pack (gzip 1472 to 804 bytes)
   ...
   POST git-upload-pack (gzip 976722 to 483608 bytes)
   POST git-upload-pack (chunked)
   error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413
   fatal: the remote end hung up unexpectedly

Maybe clone from scratch instead, but mysterious it is?
Good night, and Ciao from Germany,


github and cgit-beta repositories are not the same.  Commit hashes won't 
match so you cannot simply change the URL.


Look at this example.  Same commit with different hash:

https://github.com/freebsd/freebsd/commit/33ad4343e75940eae87391cc2198ddb617246ea3

https://cgit-beta.freebsd.org/src/commit/?id=f04d830d76bdba3c5d2f3a184a72f64413dafe44 


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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/823352/
> https://git-scm.com/docs/hash-function-transition

For those interested, additional topical from same site...

https://github.com/bk2204/git/tree/transition-stage-4

https://lwn.net/Articles/823352/
Updating the Git protocol for SHA-256

https://lwn.net/Articles/811068/
A new hash algorithm for Git

https://lwn.net/Articles/715716/
Moving Git past SHA-1


https://lwn.net/Articles/813646/
Attestation for kernel patches

https://lwn.net/Articles/821367/
Merkle trees and build systems

https://lwn.net/Articles/663875/
Changes in the TLS certificate ecosystem, part 1

https://lwn.net/Articles/468911/
Sovereign Keys for certificate verification

https://lwn.net/Articles/652580/
Decentralization for the web
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Where's the fingerprints and sigs? (was: Please check the current beta git conversions)

[grarpamp]

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, and downloads, and
packages, forums, and git hashtree initialization first hashes, and
pubkey modulus not just the larger DER's by untrusted/attacking CA's,
etc... are all not sha-256 fingerprint signed and attested to in a base
included textfile, in repo and on website, etc by security officer keys
having good WoT... for users to reference, import, validate, pin down, etc.
And tools for accessing such services often not have fingerprint
pinning options.
Woes be to those using such untrustable massively MITM'd and
spied upon networks as the Internet, Workplace, Home, Travel,
VPN, WiFi, Tor Exits, etc not having any way to authenticate
fingerprints and pin such services back to their favorite OS
project's security apostille office yet.

Security vaunted OpenBSD still serves up via cleartext non-hashtree
anoncvs on non-ecc harware on non-zfs-skein filesystems etc...

So the BSD world must still be thought secure, bit integral, and
trustably accessible without any of these infrastructure tool
fingerprint sig and pin basics... still no need to supply them since
decades since TLS/SSH/etc were deployed...

Right?

Not.

Cheers all :)

[Same for Linux ;]
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Steffen Nurpmeso]

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-upload-pack (gzip 1472 to 804 bytes)
  ...
  POST git-upload-pack (gzip 976722 to 483608 bytes)
  POST git-upload-pack (chunked)
  error: RPC failed; HTTP 413 curl 22 The requested URL returned error: 413
  fatal: the remote end hung up unexpectedly

Maybe clone from scratch instead, but mysterious it is?
Good night, and Ciao from Germany,

--steffen
|
|Der Kragenbaer,The moon bear,
|der holt sich munter   he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 checkout https://svn.freebsd.org/base/head ${HOME}/freebsd/src

git checkout https://git.freebsd.org/base/head ${HOME}/freebsd/src

> Creating diff against updated head.
>
>   svn update
>   svn diff > patch.diff

git pull
git diff >patch.diff

> Adding a new file
>
>   svn add /usr/src/libm/msun/src/_s_sinpi.c

git add /usr/src/libm/msun/src/_s_sinpi.c

> Committing a change to /usr/src
>
>   svn update
>   svn diff  | more (everyone does one last check, right?)
>   svn commit 

git pull
git add -A # add all files, even new ones
   # alternative would be "git add "
git diff --cached
git commit


I "assumed" that u...@git.freebsd.org is valid, but depending on
configuration of the server, g...@git.freebsd.org might be the right one.
Someone with actual knowledge (and I'm looking at Ed) will fill in the
right details.

If needed for any doc/example/howto, feel free to copy these examples
where suites best FreeBSD project/developers or tell me what to edit.

Regards,
meka


signature.asc
Description: PGP signature

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

[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 initial experience with the Github UI has been a disaster.

mcl
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Mark Linimon]

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/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 "short intro", 2nd sentence.
>>> 
>>> New committers are assumed to already be familiar with the basic
>>> operation of Git.  If not, start by reading the Git Book.
>> 
>> This doc started as a direct translation of the Subversion primer,
>> which has as its first sentence:
>>> New committers are assumed to already be familiar with the basic operation 
>>> of Subversion. If not, start by reading the Subversion Book.
>> 
>> As with the Subversion primer the doc is intended to provide a quick
>> reference for day-to-day commands, but not act as a reference or
>> introduction to the entire theory of operation of the associated VCS.
> 
> The rest of the guide walks people through how to do the job, but without all 
> the theory for the basics.
> 
> Again it needs some work for the advanced topic it currently just omits…
> 



Sorry, but I had to think of this:


https://xkcd.com/1597/


The project was announced a while back in the quarterly status report (that’s 
the first time I read about it at least).

It’s obviously a huge undertaking, the people taking part in it should be 
commended, not ridiculed (IMO).

For people who don’t have much exposure to git, it can be very obnoxious. 

Though these days, a lot of people assume git=github and the GUI there 
certainly makes things easier.

If it wasn’t completely riddled with security-holes, I would recommend the 
project to run its own gitlab instance - but for a project this size, you’d be 
looking at a FTE just herding that bag of cats and constantly upgrading it…



 



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 Blissma...@blisses.org
They also surf, who only stand on waves.


signature.asc
Description: PGP signature

Re: Please check the current beta git conversions

[Ulrich Spörlein]

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 instead see `du` reporting 1.2GiB just after a 
> simple clone (no options), which AFAIK contains the whole history.

That's correct, the repo size for src should be well under 2.0GiB but
could be larger locally if you still have unused refs as can still
happen with the conversion producing different commit hashes every once
in a while.

doc should be less than 500M and ports also under the 2GiB mark. It all
depends a bit on how good the repo was repacked, so I can only give
ballpark figures.

Cheers
Uli

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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.
> > 
> > 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 at all.  Unlike everyone else, he has clearly seen
> > > what the basic problem is (zero communications about this impending
> > > cutover to the people who need to work with it every day), and he
> > > summarized it in a completely practical way.
> > 
> > We disagree.  The message could have been worded without being negative.
> > 
> > > This assumption that everyone knows how to use git is mind-boggling.  I
> > > think I installed it once, a few years ago.  Then I uninstalled it
> > > because of how abysmally hard it was to try to learn even a few
> > > commands to do anything with it.
> > 
> > No, it's assumed you will learn. I did. We all can.
> > 
> > Please, we cooperate on this project. We don't attack, and yes, these were 
> > attacks. 
> > 
> > > I guess Steve & I are a couple dinosaurs and the whole rest of the
> > > freebsd user and committer community is laughing at our ignorance and
> > > thinking "we don't need their contributions anyway, so let's just mock
> > > them and move on."
> > 
> > I don't think so. I'm guessing I'm older and more set in my ways.
> > 
> > There are much better ways to communicate that in recent messages.
> > 
> 
> How typical:  trim away ALL context of what's being discussed, then
> claim that the material was offensive in some way after destroying the
> contextual evidence that makes a lie of your claim.


I apologize for the excessive trimming.

I regret posting, but still persist in my call for improved methods.

Umm, as for the rest... I don't know how to reply to that.

-- 
  Dan Langille
  d...@langille.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 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 at all.  Unlike everyone else, he has clearly seen
> > > what the basic problem is (zero communications about this impending
> > > cutover to the people who need to work with it every day), and he
> > > summarized it in a completely practical way.
> > 
> > We disagree.  The message could have been worded without being negative.
> > 
> > > This assumption that everyone knows how to use git is mind-boggling.  I
> > > think I installed it once, a few years ago.  Then I uninstalled it
> > > because of how abysmally hard it was to try to learn even a few
> > > commands to do anything with it.
> > 
> > No, it's assumed you will learn. I did. We all can.
> > 
> > Please, we cooperate on this project. We don't attack, and yes, these were 
> > attacks. 
> > 
> > > I guess Steve & I are a couple dinosaurs and the whole rest of the
> > > freebsd user and committer community is laughing at our ignorance and
> > > thinking "we don't need their contributions anyway, so let's just mock
> > > them and move on."
> > 
> > I don't think so. I'm guessing I'm older and more set in my ways.
> > 
> > There are much better ways to communicate that in recent messages.
> > 
> 
> How typical:  trim away ALL context of what's being discussed, then
> claim that the material was offensive in some way after destroying the
> contextual evidence that makes a lie of your claim.

I apologize for the excessive trimming.

I regret posting, but still persist in my call for improved methods.

Umm, as for the rest... I don't know how to reply to that.

-- 
  Dan Langille
  d...@langille.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 line.
>
> > I applaud Steve's message as being the first one in this thread that
> > has any real value at all.  Unlike everyone else, he has clearly seen
> > what the basic problem is (zero communications about this impending
> > cutover to the people who need to work with it every day), and he
> > summarized it in a completely practical way.
>
> We disagree.  The message could have been worded without being negative.
>

It could have been worded in a way that was actionable.


> > This assumption that everyone knows how to use git is mind-boggling.  I
> > think I installed it once, a few years ago.  Then I uninstalled it
> > because of how abysmally hard it was to try to learn even a few
> > commands to do anything with it.
>
> No, it's assumed you will learn. I did. We all can.
>
> Please, we cooperate on this project. We don't attack, and yes, these were
> attacks.
>
> > I guess Steve & I are a couple dinosaurs and the whole rest of the
> > freebsd user and committer community is laughing at our ignorance and
> > thinking "we don't need their contributions anyway, so let's just mock
> > them and move on."
>
> I don't think so. I'm guessing I'm older and more set in my ways.
>
> There are much better ways to communicate that in recent messages.
>

I agree. I apologize for my outburst.  Just frustrated.

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 Steve's message as being the first one in this thread that
> > has any real value at all.  Unlike everyone else, he has clearly seen
> > what the basic problem is (zero communications about this impending
> > cutover to the people who need to work with it every day), and he
> > summarized it in a completely practical way.
> 
> We disagree.  The message could have been worded without being negative.
> 
> > This assumption that everyone knows how to use git is mind-boggling.  I
> > think I installed it once, a few years ago.  Then I uninstalled it
> > because of how abysmally hard it was to try to learn even a few
> > commands to do anything with it.
> 
> No, it's assumed you will learn. I did. We all can.
> 
> Please, we cooperate on this project. We don't attack, and yes, these were 
> attacks. 
> 
> > I guess Steve & I are a couple dinosaurs and the whole rest of the
> > freebsd user and committer community is laughing at our ignorance and
> > thinking "we don't need their contributions anyway, so let's just mock
> > them and move on."
> 
> I don't think so. I'm guessing I'm older and more set in my ways.
> 
> There are much better ways to communicate that in recent messages.
> 

How typical:  trim away ALL context of what's being discussed, then
claim that the material was offensive in some way after destroying the
contextual evidence that makes a lie of your claim.

-- Ian

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 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 by reading the Git Book.
> > > >
> > > > This doc started as a direct translation of the Subversion
> > > > primer,
> > > > which has as its first sentence:
> > > > > New committers are assumed to already be familiar with the
> > > > > basic
> > >
> > > operation of Subversion. If not, start by reading the Subversion
> > > Book.
> > > >
> > > > As with the Subversion primer the doc is intended to provide a
> > > > quick
> > > > reference for day-to-day commands, but not act as a reference or
> > > > introduction to the entire theory of operation of the associated
> > > > VCS.
> > >
> > > Like GCC, which did the svn to git dance at start of the year,
> > > FreeBSD is throwing away a decade+ of corporate knowledge of
> > > working with svn and /usr/src.  What is needed is a succinct
> > > translation of the most common svn commands translated to git.
> > >
> > > 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 ...
> > >
> > > Creating diff against updated head.
> > >
> > >   svn update
> > >   svn diff > patch.diff
> > >
> > >   git ...
> > >
> > > Adding a new file
> > >
> > >   svn add /usr/src/libm/msun/src/_s_sinpi.c
> > >
> > >   git ...
> > >
> > > Committing a change to /usr/src
> > >
> > >   svn update
> > >   svn diff  | more (everyone does one last check,
> > > right?)
> > >   svn commit 
> > >
> > >   git ...
> > >
> >
> > 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 will just ignore you if
> > you make
> > too many of them like it.
> >
>
> Seriously, Warner?
>
> I applaud Steve's message as being the first one in this thread that
> has any real value at all.  Unlike everyone else, he has clearly seen
> what the basic problem is (zero communications about this impending
> cutover to the people who need to work with it every day), and he
> summarized it in a completely practical way.
>
> This assumption that everyone knows how to use git is mind-boggling.  I
> think I installed it once, a few years ago.  Then I uninstalled it
> because of how abysmally hard it was to try to learn even a few
> commands to do anything with it.
>
> I guess Steve & I are a couple dinosaurs and the whole rest of the
> freebsd user and committer community is laughing at our ignorance and
> thinking "we don't need their contributions anyway, so let's just mock
> them and move on."
>

I'm just extra grumpy today.

First, the doc has what Steve requested already, so the high level
snarkiness isn't helpful.
Second, the doc isn't done, but there was no feedback on where in the doc
it isn't clear, so the message isn't helpful.
Third, you're reading too much into the first paragraph, which was copied
verbatim from the current guide.

That's what lead to my outburst.

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 at all.  Unlike everyone else, he has clearly seen
> what the basic problem is (zero communications about this impending
> cutover to the people who need to work with it every day), and he
> summarized it in a completely practical way.

We disagree.  The message could have been worded without being negative.

> This assumption that everyone knows how to use git is mind-boggling.  I
> think I installed it once, a few years ago.  Then I uninstalled it
> because of how abysmally hard it was to try to learn even a few
> commands to do anything with it.

No, it's assumed you will learn. I did. We all can.

Please, we cooperate on this project. We don't attack, and yes, these were 
attacks. 

> I guess Steve & I are a couple dinosaurs and the whole rest of the
> freebsd user and committer community is laughing at our ignorance and
> thinking "we don't need their contributions anyway, so let's just mock
> them and move on."

I don't think so. I'm guessing I'm older and more set in my ways.

There are much better ways to communicate that in recent messages.

-- 
  Dan Langille
  d...@langille.org
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 will just ignore you if you make
> too many of them like it.
> 

I don't find it insulting at all.  I have 15+ years experience
using svn with both GCC and FreeBSD repositories.  GCC changed
from svn and git with little regard to its impact on developers
(except for those pushing the move to git).  gfortran has lost
one of its most active bug fixer/contributors because he knows
0 about git.  By extension FreeBSD lost one of the few users
that actually tried to ensure GCC works on FreeBSD (hopefully,
people don't use g++'s complex math without testing!).

-- 
Steve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 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 by reading the Git Book.
> > > 
> > > This doc started as a direct translation of the Subversion
> > > primer,
> > > which has as its first sentence:
> > > > New committers are assumed to already be familiar with the
> > > > basic
> > 
> > operation of Subversion. If not, start by reading the Subversion
> > Book.
> > > 
> > > As with the Subversion primer the doc is intended to provide a
> > > quick
> > > reference for day-to-day commands, but not act as a reference or
> > > introduction to the entire theory of operation of the associated
> > > VCS.
> > 
> > Like GCC, which did the svn to git dance at start of the year,
> > FreeBSD is throwing away a decade+ of corporate knowledge of
> > working with svn and /usr/src.  What is needed is a succinct
> > translation of the most common svn commands translated to git.
> > 
> > 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 ...
> > 
> > Creating diff against updated head.
> > 
> >   svn update
> >   svn diff > patch.diff
> > 
> >   git ...
> > 
> > Adding a new file
> > 
> >   svn add /usr/src/libm/msun/src/_s_sinpi.c
> > 
> >   git ...
> > 
> > Committing a change to /usr/src
> > 
> >   svn update
> >   svn diff  | more (everyone does one last check,
> > right?)
> >   svn commit 
> > 
> >   git ...
> > 
> 
> 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 will just ignore you if
> you make
> too many of them like it.
> 

Seriously, Warner?

I applaud Steve's message as being the first one in this thread that
has any real value at all.  Unlike everyone else, he has clearly seen
what the basic problem is (zero communications about this impending
cutover to the people who need to work with it every day), and he
summarized it in a completely practical way.

This assumption that everyone knows how to use git is mind-boggling.  I
think I installed it once, a few years ago.  Then I uninstalled it
because of how abysmally hard it was to try to learn even a few
commands to do anything with it.

I guess Steve & I are a couple dinosaurs and the whole rest of the
freebsd user and committer community is laughing at our ignorance and
thinking "we don't need their contributions anyway, so let's just mock
them and move on."

-- Ian


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 ...


"which svnlite" -> /usr/bin/svnlite
(from /usr/src/usr.bin/svn)

"which git" -> /usr/local/bin/git
(from /usr/ports/devel/git)

After the transition, will FreeBSD base contain the tool for the cloning 
the FreeBSD repository (not one of the mirrors?)


Is there a plan to have 'git' or one of its clones added to the base system?

Surprisingly, I can't seem to find any prominent discussion / debate on 
"git in base" (the tool itself).


Theron
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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-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 by reading the Git Book.
> >
> > This doc started as a direct translation of the Subversion primer,
> > which has as its first sentence:
> > > New committers are assumed to already be familiar with the basic
> operation of Subversion. If not, start by reading the Subversion Book.
> >
> > As with the Subversion primer the doc is intended to provide a quick
> > reference for day-to-day commands, but not act as a reference or
> > introduction to the entire theory of operation of the associated VCS.
>
> Like GCC, which did the svn to git dance at start of the year,
> FreeBSD is throwing away a decade+ of corporate knowledge of
> working with svn and /usr/src.  What is needed is a succinct
> translation of the most common svn commands translated to git.
>
> 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 ...
>
> Creating diff against updated head.
>
>   svn update
>   svn diff > patch.diff
>
>   git ...
>
> Adding a new file
>
>   svn add /usr/src/libm/msun/src/_s_sinpi.c
>
>   git ...
>
> Committing a change to /usr/src
>
>   svn update
>   svn diff  | more (everyone does one last check, right?)
>   svn commit 
>
>   git ...
>

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 will just ignore you if you make
too many of them like it.

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 assumed to already be familiar with the basic
> > operation of Git.  If not, start by reading the Git Book.
> 
> This doc started as a direct translation of the Subversion primer,
> which has as its first sentence:
> > New committers are assumed to already be familiar with the basic operation 
> > of Subversion. If not, start by reading the Subversion Book.
> 
> As with the Subversion primer the doc is intended to provide a quick
> reference for day-to-day commands, but not act as a reference or
> introduction to the entire theory of operation of the associated VCS.

Like GCC, which did the svn to git dance at start of the year,
FreeBSD is throwing away a decade+ of corporate knowledge of
working with svn and /usr/src.  What is needed is a succinct
translation of the most common svn commands translated to git.

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 ...

Creating diff against updated head.

  svn update
  svn diff > patch.diff

  git ...

Adding a new file

  svn add /usr/src/libm/msun/src/_s_sinpi.c

  git ...

Committing a change to /usr/src

  svn update
  svn diff  | more (everyone does one last check, right?)
  svn commit 

  git ...

-- 
Steve
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Ed Maste]

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, because it had old
leftover objects from earlier iterations of the conversion. After
cleaning those up I see 1.5GB in .git, 2.2GB including the working
tree. My .svn directory has 1.7GB of data.

If you have only one working tree then Git's disk space requirements
should be "about the same." Each additional working tree tips the
scale increasingly in GIt's favour.

If disk space is a concern you can clone with the -depth=1 option,
which avoids fetching history. I tried that just now and have a .git
directory of about 250MB.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 already be familiar with the basic
>> operation of Git.  If not, start by reading the Git Book.
> 
> This doc started as a direct translation of the Subversion primer,
> which has as its first sentence:
>> New committers are assumed to already be familiar with the basic operation 
>> of Subversion. If not, start by reading the Subversion Book.
> 
> As with the Subversion primer the doc is intended to provide a quick
> reference for day-to-day commands, but not act as a reference or
> introduction to the entire theory of operation of the associated VCS.

The rest of the guide walks people through how to do the job, but without all 
the theory for the basics.

Again it needs some work for the advanced topic it currently just omits...

Warner
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 the tree generated by the exporter,
>> ...
> 
> Somehow I've missed this development.  Reading between the lines, it
> seems that we're planning to move from svn to git, but I can't recall
> seeing any announcement on the subject.  Can you give some background?
> It would also be nice to find a HOWTO both for the migration and for
> life with git.

We’ve been talking about the transition for about 5 years now. So far, only 
people interested in git have showed up to do any work at all. Subversion has 
lost, and even Apache, the main users of it, are moving to git. We started 
early in the year with the firm plans and have been working on it since then. 
These conversations have happened all over the place, and we’ve been posting to 
developers for months now...

There’s some draft guides, but they need work which is on my plate. They are 
OK, but have some issues on the more complicated bits.

Warner

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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/
>>> https://git-scm.com/docs/hash-function-transition
>> 
>> "soon now" seems a bit vague, from what I have read on the subject,
>> whilst the local repository operations are working with SHA256 hashes,
>> it is still lacking remote transport, clones, and such.
> 
> Yes, Git will migrate to SHA256 but will not be completely finished
> sufficiently soon to matter for our needs. We'll eventually deal with
> the migration the same way as everyone else.

Note that Subversion *also* uses SHA1, and has suffered from hash
collisions. Which at some point broke the WebKit repository, because
somebody thought it was fun to tweak two PDF files to have exactly the
same SHA1.

This is why Subversion added a few hook scripts to prevent adding such
files:

https://svn.apache.org/viewvc/subversion/trunk/tools/hook-scripts/reject-known-sha1-collisions.sh?view=markup
https://svn.apache.org/viewvc/subversion/trunk/tools/hook-scripts/reject-detected-sha1-collisions.sh?view=markup

-Dimitry



signature.asc
Description: Message signed with OpenPGP

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

[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 by reading the Git Book.

This doc started as a direct translation of the Subversion primer,
which has as its first sentence:
> New committers are assumed to already be familiar with the basic operation of 
> Subversion. If not, start by reading the Subversion Book.

As with the Subversion primer the doc is intended to provide a quick
reference for day-to-day commands, but not act as a reference or
introduction to the entire theory of operation of the associated VCS.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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-transition
>
> "soon now" seems a bit vague, from what I have read on the subject,
> whilst the local repository operations are working with SHA256 hashes,
> it is still lacking remote transport, clones, and such.

Yes, Git will migrate to SHA256 but will not be completely finished
sufficiently soon to matter for our needs. We'll eventually deal with
the migration the same way as everyone else.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Olivier Certner]

> 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. The final reported bandwidth was 
991KiB/s (same transfer size).

-- 
Olivier Certner


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Olivier Certner]

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 AFAIK contains the whole history.

I have a complete mirror of SVN that I update with scripts around `svnrdump 
dump` and `svnadmin load`, and its size is 6.1GiB (I pack it regularly).

For the record, here are the sizes of the `.svn` directories of some checkouts 
I currently have:
- stable/12 at rev 355888: 1.9GiB
- stable/12 at rev 361580: 2.4GiB
- head at rev 361584: 2.7GiB
I must point out that I don't remember the exact creation history of these. It 
is probable that, to create new ones, I did full copies (`cp -a`) of an old 
one followed by `svn switch`. Don't know if this can have an influence on 
these numbers (didn't test with pristine checkouts).

Important tip: When using `du`, don't forget to pass the '-A' option, 
especially if using ZFS + compression.

-- 
Olivier Certner


___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Mathieu Arnold]

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 checkout git will require a bit more disk space
> > than svn. However, if you have two or more working trees (say, vanilla
> > FreeBSD and multiple work-in-progress trees, or head and stable
> > branches, etc.) using "git worktree" will share the .git directory and
> > in total will occupy less space than the equivalent in svn.
> 
> > I'd expect clones to take minutes, although cgit-beta is running on a
> > lower spec jail host and might have trouble if many people are cloning
> > at the same time.
> 
> 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:

  git clone --branch=main --single-branch https...

It will cut .git down to about 1.2GB.


If you do not care about the history and only want the tip of the
branch, you can also use:

  git clone --branch=main --depth 1 https...

This will cut it down even more to about 270MB.

-- 
Mathieu Arnold


signature.asc
Description: PGP signature

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

[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
> work product before committing plans...
> https://lwn.net/Articles/823352/
> https://git-scm.com/docs/hash-function-transition

"soon now" seems a bit vague, from what I have read on the subject,
whilst the local repository operations are working with SHA256 hashes,
it is still lacking remote transport, clones, and such.

-- 
Mathieu Arnold


signature.asc
Description: PGP signature

Re: Please check the current beta git conversions

[Gary Jennejohn]

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.  
>
> > > Tom 
> 
> > Not really much different from subversion. .svn in /usr/sys is also 2.5G,
> > at least for 12.1.
> >-  
> > Kevin Oberman, Part time kid herder and retired Network Engineer  
> 
> My cross-post to freebsd-...@freebsd.org was rejected because I was/am not 
> subscribed to that list.
> 
> So I deactivate that part for this post.
> 
> I just checked du /usr/src/.svn ; this is on 11.1-STABLE old system, but this 
> tree is for HEAD : 5817268 : is this 1K-blocks?  Now I think it's 512 bytes, 
> in contrast to df that shows diskspace in 1-KB blocks: confusing.  I no 
> longer track FreeBSD-11 src trees.
> 
> Now I wonder how this compares to git and hg: NetBSD plans to switch from cvs 
> to Mercurial.
> 

This is HEAD updated a short time ago (r365233):

du -sh /usr/src/.svn/
2.0G/usr/src/.svn/

-- 
Gary Jennejohn
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Thomas Mueller]

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 also 2.5G,
> at least for 12.1.
>-  
> Kevin Oberman, Part time kid herder and retired Network Engineer

My cross-post to freebsd-...@freebsd.org was rejected because I was/am not 
subscribed to that list.

So I deactivate that part for this post.

I just checked du /usr/src/.svn ; this is on 11.1-STABLE old system, but this 
tree is for HEAD : 5817268 : is this 1K-blocks?  Now I think it's 512 bytes, in 
contrast to df that shows diskspace in 1-KB blocks: confusing.  I no longer 
track FreeBSD-11 src trees.

Now I wonder how this compares to git and hg: NetBSD plans to switch from cvs 
to Mercurial.

Tom

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 like to commit to the tree generated by the exporter,
> > > ...
> > 
> > Somehow I've missed this development.
> 
> The list archive
> 
> https://lists.freebsd.org/pipermail/freebsd-git/
> 
> has additional information.
> 
> http://wiki.freebsd.org/GitWorkflow
> http://wiki.freebsd.org/UlrichSpoerlein/GitTalkDevSummit
> 
> has more. The repo: https://cgit-beta.freebsd.org/
> 
> Freshports using git:
> devgit.freshports.org
> 
> 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 by reading the Git Book.

Define "short".

-- 
Steve
20170425 https://www.youtube.com/watch?v=VWUpyCsUKR4
20161221 https://www.youtube.com/watch?v=IbCHE-hONow
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 I've missed this development.

The list archive

https://lists.freebsd.org/pipermail/freebsd-git/

has additional information.

http://wiki.freebsd.org/GitWorkflow
http://wiki.freebsd.org/UlrichSpoerlein/GitTalkDevSummit

has more. The repo: https://cgit-beta.freebsd.org/

Freshports using git:
devgit.freshports.org

A short intro on git for svn users:
https://hackmd.io/ML5TSl8mQ5-27B5eqDf7YA?view

-- 
p...@opsec.eu+49 171 3101372Now what ?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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/823352/
https://git-scm.com/docs/hash-function-transition
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

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

[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 development.  Reading between the lines, it
seems that we're planning to move from svn to git, but I can't recall
seeing any announcement on the subject.  Can you give some background?
It would also be nice to find a HOWTO both for the migration and for
life with git.

Greg
--
Sent from my desktop computer.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA


signature.asc
Description: PGP signature

Re: Please check the current beta git conversions

[Kevin Oberman]

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 a bit more disk space
> > than svn. However, if you have two or more working trees (say, vanilla
> > FreeBSD and multiple work-in-progress trees, or head and stable
> > branches, etc.) using "git worktree" will share the .git directory and
> > in total will occupy less space than the equivalent in svn.
>
> > I'd expect clones to take minutes, although cgit-beta is running on a
> > lower spec jail host and might have trouble if many people are cloning
> > at the same time.
>
> 2.5 GB in .git directory sounds crazy and incomprehensible to me.
>
> Only src tree I would be interested in now is HEAD (13-current), though I
> would also want the ports and doc trees.  Would that mollify the diskspace
> bloat?
>
> I had trouble with the ethernet and wireless network drivers in FreeBSD 12
> and 13-current, but there subsequently was a post on a big improvement to
> the network drivers for HEAD but not 12-stable.
>
> 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 also 2.5G,
at least for 12.1.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Thomas Mueller]

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 more working trees (say, vanilla
> FreeBSD and multiple work-in-progress trees, or head and stable
> branches, etc.) using "git worktree" will share the .git directory and
> in total will occupy less space than the equivalent in svn.

> I'd expect clones to take minutes, although cgit-beta is running on a
> lower spec jail host and might have trouble if many people are cloning
> at the same time.

2.5 GB in .git directory sounds crazy and incomprehensible to me.

Only src tree I would be interested in now is HEAD (13-current), though I would 
also want the ports and doc trees.  Would that mollify the diskspace bloat?

I had trouble with the ethernet and wireless network drivers in FreeBSD 12 and 
13-current, but there subsequently was a post on a big improvement to the 
network drivers for HEAD but not 12-stable.

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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Goran Mekić]

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://cgit-beta.freebsd.org/src.git freebsd-cgit-beta
Cloning into 'freebsd-cgit-beta'...
remote: Enumerating objects: 390952, done.
remote: Counting objects: 100% (390952/390952), done.
remote: Compressing objects: 100% (30728/30728), done.
remote: Total 3763254 (delta 382506), reused 360224 (delta 360224), pack-reused 
3372302
Receiving objects: 100% (3763254/3763254), 1.10 GiB | 876.00 KiB/s, done.
Resolving deltas: 100% (2984823/2984823), done.
Updating files: 100% (81780/81780), done.


Executed in   30.36 mins   fish   external
   usr time  666.58 secs  672.00 micros  666.58 secs
   sys time   30.38 secs  144.00 micros   30.38 secs


signature.asc
Description: PGP signature

Re: Please check the current beta git conversions

[Goran Mekić]

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 consistent from this point. At this
> point the Git Working Group believes the conversion represents a
> high-fidelity translation of the Subversion history, but would
> appreciate additional review in case we've missed anything.
>
> I'd ask folks with an interest in the FreeBSD repository to clone the
> beta conversion and review the converted history in the specific areas
> they are interested in - e.g., specific contrib/ software, device
> drivers, etc. This will also present our final opportunity to change
> the author map file, if necessary.
>
> The beta src tree can be cloned via:
> % git clone https://cgit-beta.freebsd.org/src.git freebsd-cgit-beta
>
> Please follow up this week if you notice any discrepancies or author
> entries that require updates.

Hello,

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). It is
probably not what you asked for, I just wanted you to know what's the speed
over here. Are there any mirrors planned? If not, is github mirror
recommended (mostly, what's the difference if I clone from cgit vs
github)?

Also, you probably want to hide gitolite-admin repo from cgit (not a biggie).

Regards,
meka


signature.asc
Description: PGP signature

Re: Please check the current beta git conversions

[Ed Maste]

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 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 more working trees (say, vanilla
FreeBSD and multiple work-in-progress trees, or head and stable
branches, etc.) using "git worktree" will share the .git directory and
in total will occupy less space than the equivalent in svn.

I'd expect clones to take minutes, although cgit-beta is running on a
lower spec jail host and might have trouble if many people are cloning
at the same time.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Ed Maste]

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 let us know how long it took
overall.

We will have mirrors set up, which will be some combination of our own
hosts, GitHub, GitLab, or other third party hosts.

The current GitHub mirror is generated from an old version of svn2git,
which misses a lot of metadata - in particular, merges (for vendor
branch updates and such) are just missing. There are also some
mistakes that originated in our Subversion mirror network that are now
stuck in the current GitHub Mirror (commits authored by "svnmir"
instead of the correct committer, for example). We expect we will
continue to have a mirror on GitHub since many folks consider it "the"
repository of open source projects. There will be a documented process
for folks to migrate from the old to the new version of the mirror
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Please check the current beta git conversions

[Shawn Webb]

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 consistent from this point. At this
> point the Git Working Group believes the conversion represents a
> high-fidelity translation of the Subversion history, but would
> appreciate additional review in case we've missed anything.
> 
> I'd ask folks with an interest in the FreeBSD repository to clone the
> beta conversion and review the converted history in the specific areas
> they are interested in - e.g., specific contrib/ software, device
> drivers, etc. This will also present our final opportunity to change
> the author map file, if necessary.
> 
> The beta src tree can be cloned via:
> % git clone https://cgit-beta.freebsd.org/src.git freebsd-cgit-beta
> 
> Please follow up this week if you notice any discrepancies or author
> entries that require updates.

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.

Thanks,

-- 
Shawn Webb
Cofounder / Security Engineer
HardenedBSD

GPG Key ID:  0xFF2E67A277F8E1FA
GPG Key Fingerprint: D206 BB45 15E0 9C49 0CF9  3633 C85B 0AF8 AB23 0FB2
https://git-01.md.hardenedbsd.org/HardenedBSD/pubkeys/src/branch/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc


signature.asc
Description: PGP signature

Re: Please check the current beta git conversions

[Poul-Henning Kamp]

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 ?


-- 
Poul-Henning Kamp   | UNIX since Zilog Zeus 3.20
p...@freebsd.org | TCP/IP since RFC 956
FreeBSD committer   | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Please check the current beta git conversions

[Ed Maste]

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 believes the conversion represents a
high-fidelity translation of the Subversion history, but would
appreciate additional review in case we've missed anything.

I'd ask folks with an interest in the FreeBSD repository to clone the
beta conversion and review the converted history in the specific areas
they are interested in - e.g., specific contrib/ software, device
drivers, etc. This will also present our final opportunity to change
the author map file, if necessary.

The beta src tree can be cloned via:
% git clone https://cgit-beta.freebsd.org/src.git freebsd-cgit-beta

Please follow up this week if you notice any discrepancies or author
entries that require updates.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"