Ulrich Spörlein wrote:
> I don't fully recall, but I think that the hg conversion was slow and
> the disk space needed was quite a bit more than git.
>
One of Mercurial's biggest design principles is immutable history (with
history rewriting disabled by default), so increased disk space compared
On 23/12/2020 13:54, Ulrich Spörlein wrote:
On Fri, 2020-12-18 at 14:02:08 +0100, Miroslav Lachman wrote:
On 25/11/2020 06:54, Thomas Mueller wrote:
NetBSD users face a similar problem with their upcoming switch from
cvs to hg (Mercurial).
Do anybody have a link to some documents stating
On Fri, 2020-12-18 at 14:02:08 +0100, Miroslav Lachman wrote:
On 25/11/2020 06:54, Thomas Mueller wrote:
NetBSD users face a similar problem with their upcoming switch from cvs to hg
(Mercurial).
Do anybody have a link to some documents stating why FreeBSD chose Git
and why NetBSD chose
> Yes. I was answering the first question asked about FreeBSD and git...
> The clincher for me was that git is better supported by third party tools
> and has gotten quite good at 'recovery from oops' which mercurial is still
> lacking in both areas. I too have used both, and I had to re clone my
On 18/12/20 14:02, Miroslav Lachman wrote:
On 25/11/2020 06:54, Thomas Mueller wrote:
NetBSD users face a similar problem with their upcoming switch from
cvs to hg (Mercurial).
Do anybody have a link to some documents stating why FreeBSD chose Git
and why NetBSD chose Mercurial? I am using
On Fri, Dec 18, 2020 at 9:24 AM Gleb Popov wrote:
>
>
> On Fri, Dec 18, 2020 at 7:50 PM Warner Losh wrote:
>
>> On Fri, Dec 18, 2020, 7:27 AM Guido Falsi wrote:
>>
>> > On 18/12/20 14:02, Miroslav Lachman wrote:
>> > > On 25/11/2020 06:54, Thomas Mueller wrote:
>> > >
>> > >> NetBSD users face
On Fri, Dec 18, 2020 at 7:50 PM Warner Losh wrote:
> On Fri, Dec 18, 2020, 7:27 AM Guido Falsi wrote:
>
> > On 18/12/20 14:02, Miroslav Lachman wrote:
> > > On 25/11/2020 06:54, Thomas Mueller wrote:
> > >
> > >> NetBSD users face a similar problem with their upcoming switch from
> > >> cvs to
On Fri, Dec 18, 2020, 7:27 AM Guido Falsi wrote:
> On 18/12/20 14:02, Miroslav Lachman wrote:
> > On 25/11/2020 06:54, Thomas Mueller wrote:
> >
> >> NetBSD users face a similar problem with their upcoming switch from
> >> cvs to hg (Mercurial).
> >
> > Do anybody have a link to some documents
> On 18 Dec 2020, at 14:02, Miroslav Lachman <000.f...@quip.cz> wrote:
>
> On 25/11/2020 06:54, Thomas Mueller wrote:
>
>> NetBSD users face a similar problem with their upcoming switch from cvs to
>> hg (Mercurial).
>
> Do anybody have a link to some documents stating why FreeBSD chose Git
On 25/11/2020 06:54, Thomas Mueller wrote:
NetBSD users face a similar problem with their upcoming switch from cvs to hg
(Mercurial).
Do anybody have a link to some documents stating why FreeBSD chose Git
and why NetBSD chose Mercurial? I am using both tools at $WORK, I am
just curious
On Wed, 2020-11-25 at 10:05:48 -0500, Shawn Webb wrote:
On Wed, Nov 25, 2020 at 04:00:50PM +0100, Baptiste Daroussin wrote:
On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote:
> On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote:
>
> > As subject - what will there be in base to interact
On Wed, Nov 25, 2020 at 8:09 AM Mark Linimon wrote:
> On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote:
> > We hope to have it finished in time for 13.0.
>
> I also feel that it should be more a "requirement".
>
> I don't see the rush in getting 13.0 out the door. There is a lot to
>
On Wed, Nov 25, 2020 at 9:25 AM Christian Weisgerber
wrote:
> On 2020-11-25, Warner Losh wrote:
>
> >> Shouldn't it be in base before the move to git?
> >
> > We will have got (from OpenBSD: Game Of Trees) in the future. It isn't
> > quite there yet, however, so it's not in base.
>
> Since got
On Wed, Nov 25, 2020 at 6:16 AM tech-lists wrote:
> Hi,
>
> On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote:
> >On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote:
> >
> >> As subject - what will there be in base to interact with the new git
> repo?
> >> I mean, right now, for svn
On 2020-11-25, Warner Losh wrote:
>> Shouldn't it be in base before the move to git?
>
> We will have got (from OpenBSD: Game Of Trees) in the future. It isn't
> quite there yet, however, so it's not in base.
Since got can't fetch from http(s) yet, there was talk of setting
up anon-ssh access.
On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote:
> We hope to have it finished in time for 13.0.
I also feel that it should be more a "requirement".
I don't see the rush in getting 13.0 out the door. There is a lot to
get working (especially in ports-land).
mcl
On Wed, Nov 25, 2020 at 04:00:50PM +0100, Baptiste Daroussin wrote:
> On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote:
> > On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote:
> >
> > > As subject - what will there be in base to interact with the new git repo?
> > > I mean, right now,
On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote:
> On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote:
>
> > As subject - what will there be in base to interact with the new git repo?
> > I mean, right now, for svn there is svnlite. What for git?
> >
>
> 'pkg add git' is your choice
Hi,
On Tue, Nov 24, 2020 at 09:59:15PM -0700, Warner Losh wrote:
On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote:
As subject - what will there be in base to interact with the new git repo?
I mean, right now, for svn there is svnlite. What for git?
'pkg add git' is your choice now.
from tech-lists:
> As subject - what will there be in base to interact with the new git repo?
> I mean, right now, for svn there is svnlite. What for git?
> Shouldn't it be in base before the move to git?
Good question, and I hope the developers and others in charge are reading your
post.
You
On Tue, Nov 24, 2020 at 2:19 PM tech-lists wrote:
> As subject - what will there be in base to interact with the new git repo?
> I mean, right now, for svn there is svnlite. What for git?
>
'pkg add git' is your choice now.
> Shouldn't it be in base before the move to git?
>
We will have got
Hi,
As subject - what will there be in base to interact with the new git repo?
I mean, right now, for svn there is svnlite. What for git?
Shouldn't it be in base before the move to git?
thanks,
--
J.
signature.asc
Description: PGP signature
22 matches
Mail list logo