= On 30 September 2015 at 08:47, Charles Forsyth <charles.forsyth@gm= ail.com> wrote:

I was being sarcastic abo= ut the portability of so much contemporary C code.

He= re's a small but representative example.

#if HAVE_SYS_TIME_H

#include <sys/time.h

#e= lif HAVE_TIME_H

#include <time.h>

#endif

#if HAVE_SYS_CLOCK_GETTIME

time_t

time_now(void)
{=C2=A0 struct timespec timespec_value;

=C2= =A0 (void) clock_gettime(CLOCK_REALTIME, &timespec_value);

=C2=A0 return timespec_value.tv_seconds;

}

#elif HAVE_SYS_GETTIMEO= FDAY

time_t

time_now(void)
{
=C2=A0 struct timeval timeval_value;

=C2=A0 (void) gettimeofday(&timeval_value, (struct ti= mezone *) NULL);

=C2=A0 return timeval_valu= e.tv_seconds;

}

#elif HAVE_SYS_TIME

time_t

time_now(void)
{
=C2=A0 time_t seconds_since_epo= ch;

=C2=A0 (void) time(&seconds_since_e= poch);

=C2=A0 return seconds_since_epoch;

}

#endif

./configu= re =C2=A0 =C2=A0# work out which HAVE_... definitions to use

Usually there are a = few more alternatives enumerated.=C2=A0 Surprisingly often, the microsecond= s or nanoseconds

value is discarded, to get= the seconds. You could just use #include <time.h> and call time(NULL= ) to get that, but where's the fun?

--001a11c384c411678d0520f250fa-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net Date: Wed, 30 Sep 2015 10:15:04 +0200 From: lucio@proxima.alt.za In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6d5fdcd8-ead9-11e9-9d60-3106f5b1d025 > I was being sarcastic about the portability of so much contemporary C code. > You can't just compile it, even in an an ANSI/POSIX environment. Philosophically, I think that we're chasing the wrong wild goose. Computer Scientists (I've been giving Dijkstra some attention, of late) ought to focus on how to get programmers to express models and algorithms accurately and let engineers figure how to translate these into Turing machines, efficiently. Instead, we let engineers dictate to sientists how to encrypt problems that are not nails so that hammers can deal with them. Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 30 Sep 2015 11:15:34 +0300 From: lego12239@yandex.ru To: 9fans@9fans.net Message-ID: <20150930081518.GA7505@localhost> References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6cf4036e-ead9-11e9-9d60-3106f5b1d025 On Tue, Sep 29, 2015 at 02:18:20PM -0300, Tiago Natel wrote: > is there someone else interested in write a git tool for plan 9 ? May be me. But now i have no time for this :-). --=20 =D0=9D=D0=B5=D0=BC=D0=B0=D0=BD=D0=BE=D0=B2 =D0=9E=D0=BB=D0=B5=D0=B3 (Nema= nov Oleg) From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <022886b6844c49907ecc899c2857c623@proxima.alt.za> To: 9fans@9fans.net Date: Wed, 30 Sep 2015 10:22:48 +0200 From: lucio@proxima.alt.za In-Reply-To: <20150930004326.bfc0d3e2dfb114330774acb6@eigenstate.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6d6f29a4-ead9-11e9-9d60-3106f5b1d025 > I have managed to get libgit2 ported to Plan 9 Contrary to all I've said so far, I think this is good. Changes to APE, maybe less so, but maybe they ARE valuable? I need to figure how to track 9atom and 9front without losing 9legacy. But I've always viewed three-way merges as daunting, never mind higher-order ones. Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: Date: Wed, 30 Sep 2015 10:25:54 +0200 Message-ID: From: hiro <23hiro@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6d73a8b2-ead9-11e9-9d60-3106f5b1d025 lucio, I don't know what you're refering to. Perhaps because I don't understand POSIX, but also to understand your abstraction I would need some more explanation. From mboxrd@z Thu Jan 1 00:00:00 1970 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (1.0) From: Brantley Coile In-reply-to: <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net> Date: Wed, 30 Sep 2015 06:01:06 -0400 Content-transfer-encoding: quoted-printable Message-id: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6d87b4ec-ead9-11e9-9d60-3106f5b1d025 How can it be a secret 'society' if there's just one member for each secret s= ociety? Sent from my iPad > On Sep 29, 2015, at 11:11 PM, erik quanstrom wrote= : >=20 >> On Tue Sep 29 12:45:25 PDT 2015, khm@sciops.net wrote: >>> On Tue, Sep 29, 2015 at 02:18:20PM -0300, Tiago Natel wrote: >>> is there someone else interested in write a git tool for plan 9 ? >>>=20 >>> []'s >>=20 >> This has been written. You just need to fill out a Secret Plan 9 Super >> Secret Society application and find three Bilderbergs to vouch for you. >=20 > it's the super secret plan 9 society here! we *hate* the sp9sss. >=20 > to the original question: i haven't used git on plan 9. sorry, i don't ha= ve > any useful info. >=20 > - erik >=20 From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <1138a165737bc8cdbae3c8ea3b06f6ec@quintile.net> From: "Steve Simon" Date: Wed, 30 Sep 2015 11:08:56 +0100 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6d98d33a-ead9-11e9-9d60-3106f5b1d025 > How can it be a secret 'society' if there's just one member for each se= cret society? That, my good man, is the biggest secret of all! =E2=98=BA -Steve From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20150929194253.GC57214@wopr.sciops.net> References: <20150929194253.GC57214@wopr.sciops.net> Date: Thu, 1 Oct 2015 23:54:27 +1000 Message-ID: From: Prof Brucee To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7bd6c4b4af213b05210b6203 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e397bbe-ead9-11e9-9d60-3106f5b1d025 --047d7bd6c4b4af213b05210b6203 Content-Type: text/plain; charset=UTF-8 And buy a t-shirt. On 30/09/2015 5:44 AM, "Kurt H Maier" wrote: > On Tue, Sep 29, 2015 at 02:18:20PM -0300, Tiago Natel wrote: > > is there someone else interested in write a git tool for plan 9 ? > > > > []'s > > This has been written. You just need to fill out a Secret Plan 9 Super > Secret Society application and find three Bilderbergs to vouch for you. > > khm > > --047d7bd6c4b4af213b05210b6203 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

And buy a t-shirt.

On 30/09/2015 5:44 AM, "Kurt H Maier" = <khm@sciops.net> wrote:

On Tue, Sep 29, 2015 at 02:= 18:20PM -0300, Tiago Natel wrote:
> is there someone else interested in write a git tool for plan 9 ?
>
> []'s

This has been written.=C2=A0 You just need to fill out a Secret Plan 9 Supe= r
Secret Society application and find three Bilderbergs to vouch for you.

khm

--047d7bd6c4b4af213b05210b6203-- From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 $2104$) From: Jeff Sickel In-Reply-To: Date: Thu, 1 Oct 2015 12:31:30 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e4b0708-ead9-11e9-9d60-3106f5b1d025 > On Sep 30, 2015, at 2:59 AM, Charles Forsyth = wrote: >=20 > Here's a small but representative example. That=E2=80=99s just an example of a C file. The joy of Git is the rest = of the requirements to actually use it: - bash - perl5 And then if you want all the fancy tools & wrappers groups seem to like = these days: - python - java - php And finally, a browser or other gui front end to make sense of it all. Free software isn=E2=80=99t so free after all. -jas From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

Date: Thu, 1 Oct 2015 18:38:00 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b5d52ca260d5205210e8290 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e4fc450-ead9-11e9-9d60-3106f5b1d025 --047d7b5d52ca260d5205210e8290 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 1 October 2015 at 18:31, Jeff Sickel wrote: > > On Sep 30, 2015, at 2:59 AM, Charles Forsyth > wrote: > > > > Here's a small but representative example. > > That=E2=80=99s just an example of a C file. I was really just writing about the difficulty of current C portability in general. I hadn't looked at the Git source code in ages. --047d7b5d52ca260d5205210e8290 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 1 October 2015 at 18:31, Jeff Sickel <jas@corpus-callosum.com= > wrote:

> = On Sep 30, 2015, at 2:59 AM, Charles Forsyth <charles.forsyth@gmail.com> wrote:
>
> Here's a small but representative example.

That=E2=80=99s just an example of a C file.=C2=A0

=
I was really just writing about the difficulty of current C portability= in general.

I hadn't looked at the Git= source code in ages.

--047d7b5d52ca260d5205210e8290-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

From: Ryan Gonzalez Date: Thu, 1 Oct 2015 12:38:31 -0500 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11440afa2788dc05210e8596 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e56f6b2-ead9-11e9-9d60-3106f5b1d025 --001a11440afa2788dc05210e8596 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable It's still free. It just takes a heck of a lot of effort to port it to other platforms after you get addicted to it. On Thu, Oct 1, 2015 at 12:31 PM, Jeff Sickel wrote: > > > On Sep 30, 2015, at 2:59 AM, Charles Forsyth > wrote: > > > > Here's a small but representative example. > > That=E2=80=99s just an example of a C file. The joy of Git is the rest o= f the > requirements to actually use it: > > - bash > - perl5 > > And then if you want all the fancy tools & wrappers groups seem to like > these days: > > - python > - java > - php > > And finally, a browser or other gui front end to make sense of it all. > > Free software isn=E2=80=99t so free after all. > > -jas > > > --=20 Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something=E2=80=99s wrong. http://kirbyfan64.github.io/ --001a11440afa2788dc05210e8596 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It's still free. It just takes a heck of a lot of effo= rt to port it to other platforms after you get addicted to it.

On Thu, Oct 1, 2015 at 1= 2:31 PM, Jeff Sickel <jas@corpus-callosum.com> wrote:<= br>

> On Sep 30, 2015, at 2:59 AM, Charles Forsyth <charles.forsyth@gmail.com> wrote:
>
> Here's a small but representative example.

That=E2=80=99s just an example of a C file.=C2=A0 The joy of Git is = the rest of the requirements to actually use it:

- bash
- perl5

And then if you want all the fancy tools & wrappers groups seem to like= these days:

- python
- java
- php

And finally, a browser or other gui front end to make sense of it all.

Free software isn=E2=80=99t so free after all.

-jas

Ryan

[ERROR]: Your autotools build= scripts are 200 lines longer than your program. Something=E2=80=99s wrong.=

http://kirbyfan64.github.io/

=C2=A0

<= /div>

--001a11440afa2788dc05210e8596-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnold@skeeve.com Message-Id: <201510011747.t91HlrSX023358@freefriends.org> Date: Thu, 1 Oct 2015 11:47:53 -0600 To: 9fans@9fans.net References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e5fd87c-ead9-11e9-9d60-3106f5b1d025 Jeff Sickel wrote: > And then if you want all the fancy tools & wrappers groups seem to like > these days: Git is best used from the command line. All the tools just get in the way. The libgit work is probably the way to go for Plan 9. Arnold From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <201510011747.t91HlrSX023358@freefriends.org> References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

<201510011747.t91HlrSX023358@freefriends.org> Date: Fri, 2 Oct 2015 10:32:46 +0200 Message-ID: From: hiro <23hiro@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e7319c8-ead9-11e9-9d60-3106f5b1d025 Is the git protocol really so huge that a native implementation wouldn't be feasible? From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

<201510011747.t91HlrSX023358@freefriends.org> From: =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= Date: Fri, 2 Oct 2015 10:57:13 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e8162a8-ead9-11e9-9d60-3106f5b1d025 On Fri, Oct 2, 2015 at 10:32 AM, hiro <23hiro@gmail.com> wrote: > Is the git protocol really so huge that a native implementation > wouldn't be feasible? The git protocol and file format is very simple. I'm sure it's easier to write something from scratch than port git. --=20 Aram H=C4=83v=C4=83rneanu From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

<201510011747.t91HlrSX023358@freefriends.org> Date: Fri, 2 Oct 2015 09:10:43 -0400 Message-ID: From: Joseph Stewart To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a1141c8e21d86e505211ee4ee Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e85ce9c-ead9-11e9-9d60-3106f5b1d025 --001a1141c8e21d86e505211ee4ee Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Here's git "rewritten" in Javascript: http://gitlet.maryrosecook.com/ -joe On Fri, Oct 2, 2015 at 4:57 AM, Aram H=C4=83v=C4=83rneanu w= rote: > On Fri, Oct 2, 2015 at 10:32 AM, hiro <23hiro@gmail.com> wrote: > > Is the git protocol really so huge that a native implementation > > wouldn't be feasible? > > The git protocol and file format is very simple. I'm sure it's easier > to write something from scratch than port git. > > -- > Aram H=C4=83v=C4=83rneanu > > --001a1141c8e21d86e505211ee4ee Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Here's git "rewritten" in Javascript:

http://gitlet.mary= rosecook.com/

-joe

On Fri, Oct 2,= 2015 at 4:57 AM, Aram H=C4=83v=C4=83rneanu <aram.h@mgk.ro> wr= ote:

On Fri, Oct 2, 2015= at 10:32 AM, hiro <23hiro@gmail.com= > wrote:
> Is the git protocol really so huge that a native implementation
> wouldn't be feasible?

The git protocol and file format is very simple. I'm sure it'= ;s easier
to write something from scratch than port git.

--
Aram H=C4=83v=C4=83rneanu

--001a1141c8e21d86e505211ee4ee-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Message-ID: From: a.regenfuss@gmx.de To: 9fans@9fans.net Content-Type: text/plain; charset=UTF-8 Date: Fri, 2 Oct 2015 16:07:23 +0200 In-Reply-To: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

<201510011747.t91HlrSX023358@freefriends.org> , Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e8aac46-ead9-11e9-9d60-3106f5b1d025 >> Is the git protocol really so huge that a native implementation >> wouldn't be feasible? >The git protocol and file format is very simple=2E I'm sure it's easier >to write something from scratch than port git=2E >Aram H=C4=83v=C4=83rneanu Is there a version control system that can be installed on Plan 9 without = having to sacrifice a virgin? I mean, venti is great, but having something similar to git or mercurial (= or even svn/cvs=2E=2E=2E) would be nice=2E adrian From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

<201510011747.t91HlrSX023358@freefriends.org>

From: =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= Date: Fri, 2 Oct 2015 16:10:38 +0200 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6e907036-ead9-11e9-9d60-3106f5b1d025 Mercurial works. --=20 Aram H=C4=83v=C4=83rneanu From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 2 Oct 2015 17:23:19 +0200 From: Steffen Nurpmeso To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20151002152319.PJ7TA0-rH%sdaoden@yandex.com> References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

In-Reply-To: User-Agent: s-nail v14.8.5-85-g582022e MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6eaaf258-ead9-11e9-9d60-3106f5b1d025 Jeff Sickel wrote: |> On Sep 30, 2015, at 2:59 AM, Charles Forsyth rsyth@gmail.com> wrote: |>=20 |> Here's a small but representative example. | |That=E2=80=99s just an example of a C file. The joy of Git is the\ | rest of the requirements to actually use it: | |- bash Isn't a POSIX shell enough for the core? I only have mksh at hand as an alternative right now, but that looks good (on my old box i think that was /bin/sh, too): ?0[sdaoden@wales git.git-no_reduce]$ for i in *.sh; do mksh -n $i;done ?0[sdaoden@wales git.git-no_reduce]$ |- perl5 That seems to have been a temporary oops from a Mr. Eric Sunshine who messed up git(1) circa at the end of June; i've ran into this, but someone else just did one or two days before me (in august?), so this really was the replacement of a working sh/sed/awk thing with the same in perl, blowing the NO_PERL configuration option for two months (and multiple releases). The shown git reference is really nice and really, really nice to look at; i've thrown away my progit chapters 6 and 9 (or so). --steffen From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: To: 9fans@9fans.net Date: Fri, 2 Oct 2015 17:51:14 +0200 From: lucio@proxima.alt.za In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6eaf3566-ead9-11e9-9d60-3106f5b1d025 > having something similar to git or mercurial (or even svn/cvs...) would be nice. CVS works adequately. It's on sources and needs some minute fixes to get the permissions exactly right: I kept getting files created with exactly NO permission bits - my last disk failure got rid of my poor efforts to fix that, so I can't even offer some bad advice. Lucio. From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <37b6b8b4eb857e58d5ff9190d178c76f@quintile.net> From: "Steve Simon" Date: Fri, 2 Oct 2015 20:27:20 +0100 To: 9fans@9fans.net In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6eb3448a-ead9-11e9-9d60-3106f5b1d025 In a previous job I put in some quite serious effort to port SVN to APE, but it is dependent on... well pretty much everything. I never managed to even get it to compile, and lost the will to live. My new employer uses svn but is about to migrate to git so I would be interested in a port, I might even get some cycles to help. -Steve From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Message-ID: From: a.regenfuss@gmx.de To: 9fans@9fans.net Content-Type: text/plain; charset=UTF-8 Date: Fri, 2 Oct 2015 23:43:13 +0200 In-Reply-To: References: Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6eb7d270-ead9-11e9-9d60-3106f5b1d025 >CVS works adequately. Thanks a lot. adrian From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Message-ID: From: a.regenfuss@gmx.de To: 9fans@9fans.net Content-Type: text/plain; charset=UTF-8 Date: Fri, 2 Oct 2015 23:56:47 +0200 In-Reply-To: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net>

<201510011747.t91HlrSX023358@freefriends.org>

, Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6ebbda64-ead9-11e9-9d60-3106f5b1d025 >Mercurial works. If you have got an installed python. adrian From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 2 Oct 2015 21:43:22 -0400 From: Kurt H Maier To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20151003014322.GB42145@wopr.sciops.net> References:

<201510011747.t91HlrSX023358@freefriends.org>

MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6ec02178-ead9-11e9-9d60-3106f5b1d025 On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de wrote: > >Mercurial works. > If you have got an installed python. that's pretty much universally the case for mercurial, yes. khm From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Fri, 2 Oct 2015 19:30:56 -0700 To: 9fans@9fans.net Message-ID: <44056fc91ed366d5282c39e96e0d61c6@brasstown.quanstro.net> In-Reply-To: <20151003014322.GB42145@wopr.sciops.net> References:

<201510011747.t91HlrSX023358@freefriends.org>

<20151003014322.GB42145@wopr.sciops.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6ec4bd00-ead9-11e9-9d60-3106f5b1d025 On Fri Oct 2 18:46:06 PDT 2015, khm@sciops.net wrote: > On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de wrote: > > >Mercurial works. > > If you have got an installed python. > > that's pretty much universally the case for mercurial, yes. well, there are some problems with ssl. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Fri, 2 Oct 2015 20:00:08 -0700 To: 9fans@9fans.net Message-ID: <72b39ad52b8833b36e70840c0e3a9e83@brasstown.quanstro.net> In-Reply-To: References: <20150929194253.GC57214@wopr.sciops.net> <950857732c74f611ab0f684badc7d987@brasstown.quanstro.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6ec9672e-ead9-11e9-9d60-3106f5b1d025 On Wed Sep 30 03:03:36 PDT 2015, brantleycoile@me.com wrote: > How can it be a secret 'society' if there's just one member for each secret society? > > Sent from my iPad > > > On Sep 29, 2015, at 11:11 PM, erik quanstrom wrote: > > > >> On Tue Sep 29 12:45:25 PDT 2015, khm@sciops.net wrote: > >>> On Tue, Sep 29, 2015 at 02:18:20PM -0300, Tiago Natel wrote: > >>> is there someone else interested in write a git tool for plan 9 ? > >>> > >>> []'s > >> > >> This has been written. You just need to fill out a Secret Plan 9 Super > >> Secret Society application and find three Bilderbergs to vouch for you. > > > > it's the super secret plan 9 society here! we *hate* the sp9sss. > > > > to the original question: i haven't used git on plan 9. sorry, i don't have > > any useful info. the members talk to themselves? - erik From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <44056fc91ed366d5282c39e96e0d61c6@brasstown.quanstro.net> References:

<201510011747.t91HlrSX023358@freefriends.org>

<20151003014322.GB42145@wopr.sciops.net> <44056fc91ed366d5282c39e96e0d61c6@brasstown.quanstro.net> Date: Fri, 2 Oct 2015 21:37:21 -0700 Message-ID: From: Nick Owens To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11411c4a078a0b05212bd641 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6ecf234e-ead9-11e9-9d60-3106f5b1d025 --001a11411c4a078a0b05212bd641 Content-Type: text/plain; charset=UTF-8 9front now supports tls 1.2 in libsec/devtls. Mercurial can make use of it through webfs. On Oct 2, 2015 7:35 PM, "erik quanstrom" wrote: > On Fri Oct 2 18:46:06 PDT 2015, khm@sciops.net wrote: > > On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de wrote: > > > >Mercurial works. > > > If you have got an installed python. > > > > that's pretty much universally the case for mercurial, yes. > > well, there are some problems with ssl. > > - erik > > --001a11411c4a078a0b05212bd641 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

9front now supports tls 1.2 in libsec/devtls. Mercurial can = make use of it through webfs.

On Oct 2, 2015 7:35 PM, "erik quanstrom&quo= t; <quanstro@quanstro.net&g= t; wrote:

On Fri O= ct=C2=A0 2 18:46:06 PDT 2015, khm@sciops.= net wrote:
> On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de wrote:
> > >Mercurial works.
> > If you have got an installed python.
>
> that's pretty much universally the case for mercurial, yes.

well, there are some problems with ssl.

- erik

--001a11411c4a078a0b05212bd641-- From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 2 Oct 2015 21:48:29 -0700 Message-ID: From: erik quanstrom To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> MIME-Version: 1.0 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: base64 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6fa22dde-ead9-11e9-9d60-3106f5b1d025 PHAgZGlyPSJsdHIiPmRpZCB5b3UgZml4IHRoZSBTU0wgaW50ZXJmYWNlIGluIHB5dGhvbiwgdG9v PyZuYnNwOyA8L3A+CjxwIGRpcj0ibHRyIj4tIGVyaWs8YnI+CjwvcD4KPGRpdiBjbGFzcz0iZ21h aWxfcXVvdGUiPk9uIE9jdCAyLCAyMDE1IDk6MzcgUE0sIE5pY2sgT3dlbnMgJmx0O21pc2NoaWVm QG9mZmJsYXN0Lm9yZyZndDsgd3JvdGU6PGJyIHR5cGU9J2F0dHJpYnV0aW9uJz48YmxvY2txdW90 ZSBjbGFzcz0icXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVmdDoxcHgg I2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij48cCBkaXI9Imx0ciI+OWZyb250IG5vdyBzdXBw b3J0cyB0bHMgMS4yIGluIGxpYnNlYy9kZXZ0bHMuIE1lcmN1cmlhbCBjYW4gbWFrZSB1c2Ugb2Yg aXQgdGhyb3VnaCB3ZWJmcy48L3A+DQo8ZGl2IGNsYXNzPSJlbGlkZWQtdGV4dCI+T24gT2N0IDIs IDIwMTUgNzozNSBQTSwgJiMzNDtlcmlrIHF1YW5zdHJvbSYjMzQ7ICZsdDs8YSBocmVmPSJtYWls dG86cXVhbnN0cm8mIzY0O3F1YW5zdHJvLm5ldCI+cXVhbnN0cm8mIzY0O3F1YW5zdHJvLm5ldDwv YT4mZ3Q7IHdyb3RlOjxiciAvPjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW46MCAwIDAgMC44ZXg7 Ym9yZGVyLWxlZnQ6MXB4ICNjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OjFleCI+T24gRnJpIE9jdMKg IDIgMTg6NDY6MDYgUERUIDIwMTUsIDxhIGhyZWY9Im1haWx0bzpraG0mIzY0O3NjaW9wcy5uZXQi PmtobSYjNjQ7c2Npb3BzLm5ldDwvYT4gd3JvdGU6PGJyIC8+DQomZ3Q7IE9uIEZyaSwgT2N0IDAy LCAyMDE1IGF0IDExOjU2OjQ3UE0gJiM0MzswMjAwLCA8YSBocmVmPSJtYWlsdG86YS5yZWdlbmZ1 c3MmIzY0O2dteC5kZSI+YS5yZWdlbmZ1c3MmIzY0O2dteC5kZTwvYT4gd3JvdGU6PGJyIC8+DQom Z3Q7ICZndDsgJmd0O01lcmN1cmlhbCB3b3Jrcy48YnIgLz4NCiZndDsgJmd0OyBJZiB5b3UgaGF2 ZSBnb3QgYW4gaW5zdGFsbGVkIHB5dGhvbi48YnIgLz4NCiZndDs8YnIgLz4NCiZndDsgdGhhdCYj Mzk7cyBwcmV0dHkgbXVjaCB1bml2ZXJzYWxseSB0aGUgY2FzZSBmb3IgbWVyY3VyaWFsLCB5ZXMu PGJyIC8+DQo8YnIgLz4NCndlbGwsIHRoZXJlIGFyZSBzb21lIHByb2JsZW1zIHdpdGggc3NsLjxi ciAvPg0KPGJyIC8+DQotIGVyaWs8YnIgLz4NCjxiciAvPg0KPC9ibG9ja3F1b3RlPjwvZGl2Pg0K DQo8L2Jsb2NrcXVvdGU+PC9kaXY+ From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 $2104$) From: Andrew Simmons In-Reply-To: Date: Sat, 3 Oct 2015 18:03:39 +1300 Content-Transfer-Encoding: quoted-printable Message-Id: <2DF7818D-9F4F-4A5C-9F3F-5E199AC1249D@gmail.com> References: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6fa7726c-ead9-11e9-9d60-3106f5b1d025 Well, colour me confused. I can make no sense of this thread. Would = that Boyd were here to explain it. > On Oct 3, 2015, at 5:48 pm, erik quanstrom = wrote: >=20 > did you fix the SSL interface in python, too?=20 >=20 > - erik > On Oct 2, 2015 9:37 PM, Nick Owens wrote: > 9front now supports tls 1.2 in libsec/devtls. Mercurial can make use = of it through webfs. >=20 > On Oct 2, 2015 7:35 PM, "erik quanstrom" = wrote: > On Fri Oct 2 18:46:06 PDT 2015, khm@sciops.net wrote: > > On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de wrote: > > > >Mercurial works. > > > If you have got an installed python. > > > > that's pretty much universally the case for mercurial, yes. >=20 > well, there are some problems with ssl. >=20 > - erik >=20 From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <2DF7818D-9F4F-4A5C-9F3F-5E199AC1249D@gmail.com> References: <2DF7818D-9F4F-4A5C-9F3F-5E199AC1249D@gmail.com> Date: Sat, 3 Oct 2015 01:19:57 -0400 Message-ID: From: Jacob Todd To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a113ecb5a6dad5505212c6ea8 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6fab4306-ead9-11e9-9d60-3106f5b1d025 --001a113ecb5a6dad5505212c6ea8 Content-Type: text/plain; charset=UTF-8 you can use mercurial on plan 9 with python installed, not hard to understand --001a113ecb5a6dad5505212c6ea8 Content-Type: text/html; charset=UTF-8

you can use mercurial on plan 9 with python installed, not hard to understand

--001a113ecb5a6dad5505212c6ea8-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Sickel Content-Type: multipart/alternative; boundary="Apple-Mail=_E0CB4CB4-5479-4E17-AB28-BF4760F389AD" Message-Id: Mime-Version: 1.0 (Mac OS X Mail 8.2 $2104$) Date: Sat, 3 Oct 2015 14:26:34 -0500 References: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> In-Reply-To: Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6fb139d2-ead9-11e9-9d60-3106f5b1d025 --Apple-Mail=_E0CB4CB4-5479-4E17-AB28-BF4760F389AD Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Not unless they forked the fork and fixed the ssl module in the Python = 2.7.9-plan9 branch. I=E2=80=99ve not had the time nor energy to finish it off yet. -jas > On Oct 2, 2015, at 11:48 PM, erik quanstrom = wrote: >=20 > did you fix the SSL interface in python, too?=20 >=20 > - erik > On Oct 2, 2015 9:37 PM, Nick Owens wrote: > 9front now supports tls 1.2 in libsec/devtls. Mercurial can make use = of it through webfs. >=20 > On Oct 2, 2015 7:35 PM, "erik quanstrom" > wrote: > On Fri Oct 2 18:46:06 PDT 2015, khm@sciops.net = wrote: > > On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de = wrote: > > > >Mercurial works. > > > If you have got an installed python. > > > > that's pretty much universally the case for mercurial, yes. >=20 > well, there are some problems with ssl. >=20 > - erik >=20 --Apple-Mail=_E0CB4CB4-5479-4E17-AB28-BF4760F389AD Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Not unless they forked the fork and fixed the ssl module in = the Python 2.7.9-plan9 branch.

I=E2=80=99ve not had the time nor energy to finish it off = yet.

-jas

On Oct 2, 2015, at 11:48 PM, = erik quanstrom <quanstro@quanstro.net> wrote:

did you fix the SSL interface in python, too?
- erik

On Oct 2, 2015 9:37 PM, Nick Owens <mischief@offblast.org> wrote:
9front now supports tls 1.2 in libsec/devtls. Mercurial can = make use of it through webfs.

On Oct 2, 2015 7:35 PM, "erik quanstrom" = <quanstro@quanstro.net> wrote:
On Fri Oct 2 18:46:06 PDT 2015, khm@sciops.net wrote:
> On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de = wrote:
> > >Mercurial works.
> > If you have got an installed python.
>
> that's pretty much universally the case for mercurial, yes.

well, there are some problems with ssl.

- erik

= --Apple-Mail=_E0CB4CB4-5479-4E17-AB28-BF4760F389AD-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References:

Date: Sat, 3 Oct 2015 15:57:31 -0400 Message-ID: From: Jacob Todd To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a113ecb5acb318f052138b03e Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6fb8442a-ead9-11e9-9d60-3106f5b1d025 --001a113ecb5acb318f052138b03e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable that's all we use on 9front, though they might be using a different version= . On Oct 3, 2015 3:29 PM, "Jeff Sickel" wrote: > Not unless they forked the fork and fixed the ssl module in the Python > 2.7.9-plan9 branch. > > I=E2=80=99ve not had the time nor energy to finish it off yet. > > -jas > > On Oct 2, 2015, at 11:48 PM, erik quanstrom wrote= : > > did you fix the SSL interface in python, too? > > - erik > On Oct 2, 2015 9:37 PM, Nick Owens wrote: > > 9front now supports tls 1.2 in libsec/devtls. Mercurial can make use of i= t > through webfs. > On Oct 2, 2015 7:35 PM, "erik quanstrom" wrote: > > On Fri Oct 2 18:46:06 PDT 2015, khm@sciops.net wrote: > > On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de wrote: > > > >Mercurial works. > > > If you have got an installed python. > > > > that's pretty much universally the case for mercurial, yes. > > well, there are some problems with ssl. > > - erik > > > --001a113ecb5acb318f052138b03e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

that's all we use on 9front, though they might be using = a different version.

On Oct 3, 2015 3:29 PM, "Jeff Sickel" = <jas@corpus-callosum.com&= gt; wrote:

Not unless they forked the fork and fixed the s= sl module in the Python 2.7.9-plan9 branch.

I=E2=80=99ve= not had the time nor energy to finish it off yet.

-jas

On Oct 2, 2015, at = 11:48 PM, erik quanstrom <quanstro@quanstro.net> wrote:

did you fix the SSL interface in python, too?=C2=A0
= - erik

On Oct 2, 2015 9:37 PM, Nick Owens <mischief@offblast.org> wrote:
9front now su= pports tls 1.2 in libsec/devtls. Mercurial can make use of it through webfs= .

On Oct 2, 2015 7:35 PM, "erik quanstrom" <quanstro@quanstro.net> w= rote:
On Fri Oct=C2=A0 2 18:46:06 PDT 2015, khm@sciops.net wrote:
> On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de wrote:
> > >Mercurial works.
> > If you have got an installed python.
>
> that's pretty much universally the case for mercurial, yes.

well, there are some problems with ssl.

- erik

--001a113ecb5acb318f052138b03e-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References:

Date: Mon, 5 Oct 2015 15:24:04 +1100 Message-ID: From: Prof Brucee To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b2e41be2e53ff052153e2c0 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 6fc775f8-ead9-11e9-9d60-3106f5b1d025 --047d7b2e41be2e53ff052153e2c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Just buy a tshirt. On 04/10/2015 6:59 AM, "Jacob Todd" wrote: > that's all we use on 9front, though they might be using a different > version. > On Oct 3, 2015 3:29 PM, "Jeff Sickel" wrote: > >> Not unless they forked the fork and fixed the ssl module in the Python >> 2.7.9-plan9 branch. >> >> I=E2=80=99ve not had the time nor energy to finish it off yet. >> >> -jas >> >> On Oct 2, 2015, at 11:48 PM, erik quanstrom >> wrote: >> >> did you fix the SSL interface in python, too? >> >> - erik >> On Oct 2, 2015 9:37 PM, Nick Owens wrote: >> >> 9front now supports tls 1.2 in libsec/devtls. Mercurial can make use of >> it through webfs. >> On Oct 2, 2015 7:35 PM, "erik quanstrom" wrote: >> >> On Fri Oct 2 18:46:06 PDT 2015, khm@sciops.net wrote: >> > On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de wrote: >> > > >Mercurial works. >> > > If you have got an installed python. >> > >> > that's pretty much universally the case for mercurial, yes. >> >> well, there are some problems with ssl. >> >> - erik >> >> >> --047d7b2e41be2e53ff052153e2c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Just buy a tshirt.

On 04/10/2015 6:59 AM, "Jacob Todd" &l= t;jaketodd422@gmail.com> wr= ote:

= that's all we use on 9front, though they might be using a different ver= sion.

On Oct 3, 2015 3:29 PM, "Jeff Sickel" = <jas@corpus= -callosum.com> wrote:
Not unless they forked the for= k and fixed the ssl module in the Python 2.7.9-plan9 branch.

=
I=E2=80=99ve not had the time nor energy to finish it off yet.

-jas

On= Oct 2, 2015, at 11:48 PM, erik quanstrom <quanstro@quanstro.net> wrote:
did you fix the SSL interface in python, too?=C2=A0
- erik

On Oct 2, 2015 9:37 PM, Nick Owens <mischief@offblast.org> wrote:
9front now su= pports tls 1.2 in libsec/devtls. Mercurial can make use of it through webfs= .

On Oct 2, 2015 7:35 PM, "erik quanstrom" <quanstro@quanstro.net> w= rote:
On Fri Oct=C2=A0 2 18:46:06 PDT 2015, khm@sciops.net wrote:
> On Fri, Oct 02, 2015 at 11:56:47PM +0200, a.regenfuss@gmx.de wrote:
> > >Mercurial works.
> > If you have got an installed python.
>
> that's pretty much universally the case for mercurial, yes.

well, there are some problems with ssl.

- erik

--047d7b2e41be2e53ff052153e2c0-- From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 6 Oct 2015 22:37:12 -0400 From: sl@9front.org To: 9fans@9fans.net Message-ID: <385c85ca703ac8d441c4227d1bb24643@u2.inri> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 7100a516-ead9-11e9-9d60-3106f5b1d025 > My new employer uses svn but is about to migrate to git so I would > be interested in a port, I might even get some cycles to help. I'm no help here, but one of the Harvey guys (pre-Harvey) apparently built git for Plan 9. Unfortunately, only the 386 binaries were made available, no source code. I think this may just be because the repository I found was not the source repository. Anyway: http://marcus.biz.tm/hg/gnubin The git binary seems to run. I'm not sure if it works. sl From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <385c85ca703ac8d441c4227d1bb24643@u2.inri> References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> Date: Wed, 7 Oct 2015 17:17:23 +0200 Message-ID: From: =?UTF-8?Q?=C3=81lvaro_Jurado?= To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c260ce55a3390521853e64 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 711b9880-ead9-11e9-9d60-3106f5b1d025 --001a11c260ce55a3390521853e64 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Source should be in the same site, just add /files to hostname and look for tgz. I think 1.5.8.3, last year version. It was built with gcc 4.8 port for plan9 (static). You'll need some kind of ksh to use it, git has many shell scripts. It works with go get but sometimes it fails miserably retrieving packages because it has an strong dependency of fsync to freeze sha keys in fs during fetching. And that is just a dummy in Plan 9 ape. I used fflush trying to make some tweak and disabling one sha check (it does 4 or 5) to bypass that symptom, but finally I was bored at the end. I still use it to go get, but it needs a deeply review and an upgrade. =C3=81lvaro El 07/10/2015 04:37, escribi=C3=B3: > > My new employer uses svn but is about to migrate to git so I would > > be interested in a port, I might even get some cycles to help. > > I'm no help here, but one of the Harvey guys (pre-Harvey) apparently > built git for Plan 9. Unfortunately, only the 386 binaries were made > available, no source code. I think this may just be because the > repository I found was not the source repository. Anyway: > > http://marcus.biz.tm/hg/gnubin > > The git binary seems to run. I'm not sure if it works. > > sl > > --001a11c260ce55a3390521853e64 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Source should be in the same site, just add /files to hostna= me and look for tgz. I think 1.5.8.3, last year version.

It was built with gcc 4.8 port for plan9 (static). You'l= l need some kind of ksh to use it, git has many shell scripts.
It works with go get but sometimes it fails miserably retrieving packages b= ecause it has an strong dependency of fsync to freeze sha keys in fs during= fetching. And that is just a dummy in Plan 9 ape. I used fflush trying to = make some tweak and disabling one sha check (it does 4 or 5) to bypass that= symptom, but finally I was bored at the end.

I still use it to go get, but it needs a deeply review and a= n upgrade.

=C3=81lvaro

El 07/10/2015 04:37, <sl@9front.org> escribi=C3=B3:
> My new employer uses svn but is about to m= igrate to git so I would
> be interested in a port, I might even get some cycles to help.

I'm no help here, but one of the Harvey guys (pre-Harvey) apparently built git for Plan 9. Unfortunately, only the 386 binaries were made
available, no source code. I think this may just be because the
repository I found was not the source repository. Anyway:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 http://marcus.biz.tm/hg/gnubin

The git binary seems to run. I'm not sure if it works.

sl

--001a11c260ce55a3390521853e64-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> Date: Wed, 7 Oct 2015 17:24:17 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b5d52ca9ad2040521862dc0 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 7133345e-ead9-11e9-9d60-3106f5b1d025 --047d7b5d52ca9ad2040521862dc0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 7 October 2015 at 16:17, =C3=81lvaro Jurado wrote= : > because it has an strong dependency of fsync to freeze sha keys in fs > during fetching. And that is just a dummy in Plan 9 ape fsync causes any operating system buffers in the "buffer cache" to be flushed to "disk" (not user-space buffers), so nothing should be needed with plan 9, which is why fsync is a nop in APE. --047d7b5d52ca9ad2040521862dc0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 7 October 2015 at 16:17, =C3=81lvaro Jurado <elbingmiss@gmail.com> wrote:

because it has an st= rong dependency of fsync to freeze sha keys in fs during fetching. And that= is just a dummy in Plan 9 ape

fsync causes any opera= ting system buffers in the "buffer cache" to be flushed to "= disk" (not user-space buffers), so nothing should be needed with plan = 9, which is why fsync is a nop in APE.

--047d7b5d52ca9ad2040521862dc0-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> Date: Wed, 7 Oct 2015 23:23:22 +0200 Message-ID: From: =?UTF-8?Q?=C3=81lvaro_Jurado?= To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11407d1e39391205218a5b68 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 71471636-ead9-11e9-9d60-3106f5b1d025 --001a11407d1e39391205218a5b68 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yes, it has no sense in Plan 9, I know, thanks. I was talking about ape lib because is what was used to port git in my case. I even found a Rob's old mail answering a similar question saying that it's a matter of file server (I can't remember original question). And there are many debates around internet about fsync, with fans an detractors. In previous versions of git, there weren't fsyncs to freeze keys, but Linus wanted to change old git behaviour at one moment, 1.8 version I think. And after all, problem is still there in this case, there's no way to ensure if an fd is in the heaven of bits or in any place in fs at the moment of fopen issue by git, breaking its behaviour over Plan 9. =C3=81lvaro El 07/10/2015 18:26, "Charles Forsyth" escribi= =C3=B3: > > On 7 October 2015 at 16:17, =C3=81lvaro Jurado wro= te: > >> because it has an strong dependency of fsync to freeze sha keys in fs >> during fetching. And that is just a dummy in Plan 9 ape > > > fsync causes any operating system buffers in the "buffer cache" to be > flushed to "disk" (not user-space buffers), so nothing should be needed > with plan 9, which is why fsync is a nop in APE. > --001a11407d1e39391205218a5b68 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Yes, it has no sense in Plan 9, I know, thanks. I was talkin= g about ape lib because is what was used to port git in my case.

I even found a Rob's old mail answering a similar questi= on saying that it's a matter of file server (I can't remember origi= nal question). And there are many debates around internet about fsync, with= fans an detractors.

In previous versions of git, there weren't fsyncs to fre= eze keys, but Linus wanted to change old git behaviour at one moment, 1.8 v= ersion I think. And after all, problem is still there in this case, there&#= 39;s no way to ensure if an fd is in the heaven of bits or in any place in = fs at the moment of fopen issue by git, breaking its behaviour over Plan 9.=

=C3=81lvaro

El 07/10/2015 18:26, "Charles Forsyth"= <charles.forsyth@gmail.com= > escribi=C3=B3:

On 7 October 2015 at 16:17, =C3=81lvaro Jurado <elbingmiss@gmail.co= m> wrote:
because it has a= n strong dependency of fsync to freeze sha keys in fs during fetching. And = that is just a dummy in Plan 9 ape

fsync causes any o= perating system buffers in the "buffer cache" to be flushed to &q= uot;disk" (not user-space buffers), so nothing should be needed with p= lan 9, which is why fsync is a nop in APE.

--001a11407d1e39391205218a5b68-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sat, 10 Oct 2015 08:23:26 -0700 To: 9fans@9fans.net Message-ID: <8675dd67db7f50f93257f1df50e73767@lilly.quanstro.net> In-Reply-To: References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 71ab8f6c-ead9-11e9-9d60-3106f5b1d025 On Wed Oct 7 14:25:58 PDT 2015, elbingmiss@gmail.com wrote: > Yes, it has no sense in Plan 9, I know, thanks. I was talking about ape lib > because is what was used to port git in my case. > > I even found a Rob's old mail answering a similar question saying that it's > a matter of file server (I can't remember original question). And there are > many debates around internet about fsync, with fans an detractors. > > In previous versions of git, there weren't fsyncs to freeze keys, but Linus > wanted to change old git behaviour at one moment, 1.8 version I think. And > after all, problem is still there in this case, there's no way to ensure if > an fd is in the heaven of bits or in any place in fs at the moment of fopen > issue by git, breaking its behaviour over Plan 9. so we have these facts 1. git worked without the fsync, 2. on plan 9, fsync is unnecessary yet, the agument is: because ape fsync, git is broken on plan 9? i'm afraid i don't understand this reasoning. also, directly to the "heaven of bits". i assume you mean the data in the file to which the fd points. all unix-like systems provide some consistency guarantees. if a file is manipulated by a single program on a single machine, there will always be a strongly coherent view of the file. perhaps there is some confusion between the system call interface, which uses file desciptors and stdio, which does do read and write buffering? fsync doesn't take care of that, either. in the case of system crash, fsync doesn't provide strong guarantees that the write will not be lost, or the fs not corrupted even in linux. some versions of the linux kernel do nothing on fsync, fsync doesn't actually put data on disk https://lwn.net/Articles/270891/ and some options for ext make fsyncs useless https://lwn.net/Articles/328363/ - erik From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Sat, 10 Oct 2015 08:26:57 -0700 To: 9fans@9fans.net Message-ID: <9c545c7fbde6ddecb82def2dc66194ed@lilly.quanstro.net> In-Reply-To: References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 71baeab6-ead9-11e9-9d60-3106f5b1d025 > It works with go get but sometimes it fails miserably retrieving packages > because it has an strong dependency of fsync to freeze sha keys in fs > during fetching. And that is just a dummy in Plan 9 ape. I used fflush i believe the problem has been misdiagnosed. fsync can't be the issue, since there are no such buffers on plan 9. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <9c545c7fbde6ddecb82def2dc66194ed@lilly.quanstro.net> References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> <9c545c7fbde6ddecb82def2dc66194ed@lilly.quanstro.net> Date: Sat, 10 Oct 2015 20:25:50 +0200 Message-ID: From: =?UTF-8?Q?=C3=81lvaro_Jurado?= To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e01182d96d0e0330521c439bf Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 72424592-ead9-11e9-9d60-3106f5b1d025 --089e01182d96d0e0330521c439bf Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Agree at all. As I said, after some time fighting with it I was bored. I remember asking you in g+ about fsync issues when I was working on it. In fact it fails for example, if you clone go repo and then checkout a branch. While checking out it looses in any moment some sha key and then fatal. Other times not. I used an ape libs compiled with gcc and gnu toolchain port, but that means one can use normal ape to have working. Libs are the same. Inside, it's hellish. Full of redundant code and configure "tool" does not make all the work. You will need to tweak adding things in conf file generated. It uses many shell scripts and it's designed to have many symlinks to git binary, what does you have many git clones with different names unless you hack install part of the makefile. If it doesn't detect a working ln, it does a cp. I never got 2.x versions working, sha key mess was changed after 2.0. About fsync, I'm not a fan, I wasn't blaming plan9 in anyway. It can go jump to a lake. =C3=81lvaro El 10/10/2015 17:27, "erik quanstrom" escribi=C3=B3= : > > It works with go get but sometimes it fails miserably retrieving packag= es > > because it has an strong dependency of fsync to freeze sha keys in fs > > during fetching. And that is just a dummy in Plan 9 ape. I used fflush > > i believe the problem has been misdiagnosed. fsync can't be the issue, > since there are no such buffers on plan 9. > > - erik > > --089e01182d96d0e0330521c439bf Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Agree at all. As I said, after some time fighting with it I = was bored. I remember asking you in g+ about fsync issues when I was workin= g on it.

In fact it fails for example, if you clone go repo and then = checkout a branch. While checking out it looses in any moment some sha key = and then fatal. Other times not.

I used an ape libs compiled with gcc and gnu toolchain port,= but that means one can use normal ape to have working. Libs are the same.<= /p>

Inside, it's hellish. Full of redundant code and configu= re "tool" does not make all the work. You will need to tweak addi= ng things in conf file generated. It uses many shell scripts and it's d= esigned to have many symlinks to git binary, what does you have many git cl= ones with different names unless you hack install part of the makefile. If = it doesn't detect a working ln, it does a cp.

I never got 2.x versions working, sha key mess was changed a= fter 2.0.

About fsync, I'm not a fan, I wasn't blaming plan9 i= n anyway. It can go jump to a lake.

=C3=81lvaro

El 10/10/2015 17:27, "erik quanstrom" = <quanstro@quanstro.net> = escribi=C3=B3:

> = It works with go get but sometimes it fails miserably retrieving packages > because it has an strong dependency of fsync to freeze sha keys in fs<= br> > during fetching. And that is just a dummy in Plan 9 ape. I used fflush=

i believe the problem has been misdiagnosed.=C2=A0 fsync can't be the i= ssue,
since there are no such buffers on plan 9.

- erik

--089e01182d96d0e0330521c439bf-- From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 12 Oct 2015 13:37:22 +0200 From: Steffen Nurpmeso To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Message-ID: <20151012113722.LaRyrA_0L%sdaoden@yandex.com> References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> <8675dd67db7f50f93257f1df50e73767@lilly.quanstro.net> In-Reply-To: <8675dd67db7f50f93257f1df50e73767@lilly.quanstro.net> User-Agent: s-nail v14.8.5-106-gf8740e1 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 7283d00c-ead9-11e9-9d60-3106f5b1d025 erik quanstrom wrote: |On Wed Oct 7 14:25:58 PDT 2015, elbingmiss@gmail.com wrote: |in the case of system crash, fsync doesn't provide strong \ |guarantees that the |write will not be lost, or the fs not corrupted even in li\ |nux. some versions of |the linux kernel do nothing on fsync, fsync doesn't actual\ Linux fsync(2) says that the file itself is fine after it, but for the filesystem metadata you need an additional fsync(2) on the directory the file resides in. The final wording of the related POSIX issue[1] states that the latter is only necessary if directory entries have been created or removed (also regarding rename(2) which needs two fsync(2) calls; luckily we're binary only), and noone has opposed to this wording in more than two years. (Mac OS X Snow Leopard had a F_FULLFSYNC fcntl(2) which provided the fully-synced guarantee, as in _os_fsync = os.fsync def __fullfsync(fd): if not SAFE_FSYNC: return _os_fsync(fd) try: fcntl.fcntl(fd, fcntl.F_FULLFSYNC) except IOError as e: if e.errno == errno.ENOTTY: return _os_fsync(fd) raise os.fsync = __fullfsync which i thought of as a good idea, from a programmers point of view who wants to get it done.) [1] http://austingroupbugs.net/view.php?id=672#c1618 --steffen From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> <9c545c7fbde6ddecb82def2dc66194ed@lilly.quanstro.net> Date: Mon, 12 Oct 2015 12:47:16 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e013c6b6214f6b40521e6e404 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 72e9bb6a-ead9-11e9-9d60-3106f5b1d025 --089e013c6b6214f6b40521e6e404 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 10 October 2015 at 19:25, =C3=81lvaro Jurado wrot= e: > While checking out it looses in any moment some sha key and then fatal. > Other times not. Why do you think that was fsync, and not something else? --089e013c6b6214f6b40521e6e404 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 10 October 2015 at 19:25, =C3=81lvaro Jurado <elbingmiss@gmail.com> wrote:

While checking out i= t looses in any moment some sha key and then fatal. Other times not.

Why do =C2=A0you think that was fsync, and not something el= se?

--089e013c6b6214f6b40521e6e404-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> <9c545c7fbde6ddecb82def2dc66194ed@lilly.quanstro.net>

Date: Mon, 12 Oct 2015 18:49:35 +0200 Message-ID: From: =?UTF-8?Q?=C3=81lvaro_Jurado?= To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=089e01182d9648f0dc0521eb1dde Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 72fe9ed6-ead9-11e9-9d60-3106f5b1d025 --089e01182d9648f0dc0521eb1dde Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I remember tracing entire clone process. It was hanging in a function (don't remember which, the only one has fsync) what ensures sha key is in fs. I bypassed it with a rare mess, so if key is there, it works, if not, fails. In fact fsync changes introduced by Linus was in the line of ensuring that key is there to decompress package. Maybe I was wrong. When I'll back to port git for Harvey, I'll see. =C3=81lvaro El 12/10/2015 13:49, "Charles Forsyth" escribi= =C3=B3: > > On 10 October 2015 at 19:25, =C3=81lvaro Jurado wr= ote: > >> While checking out it looses in any moment some sha key and then fatal. >> Other times not. > > > Why do you think that was fsync, and not something else? > > --089e01182d9648f0dc0521eb1dde Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

I remember tracing entire clone process. It was hanging in a= function (don't remember which, the only one has fsync) what ensures s= ha key is in fs. I bypassed it with a rare mess, so if key is there, it wor= ks, if not, fails. In fact fsync changes introduced by Linus was in the lin= e of ensuring that key is there to decompress package.
Maybe I was wrong. When I'll back to port git for Harvey, I'll see.=

=C3=81lvaro

El 12/10/2015 13:49, "Charles Forsyth"= <charles.forsyth@gmail.com= > escribi=C3=B3:

On 10 October 2015 at 19:25, =C3=81lvaro Jurado <<= a href=3D"mailto:elbingmiss@gmail.com" target=3D"_blank">elbingmiss@gmail.c= om> wrote:
While checking o= ut it looses in any moment some sha key and then fatal. Other times not.

Why do =C2=A0you think that was fsync, and not somethin= g else?

--089e01182d9648f0dc0521eb1dde-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> <9c545c7fbde6ddecb82def2dc66194ed@lilly.quanstro.net>

Date: Mon, 12 Oct 2015 18:00:11 +0100 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c1b90e34c4b10521eb43ef Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 7302baa2-ead9-11e9-9d60-3106f5b1d025 --001a11c1b90e34c4b10521eb43ef Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 12 October 2015 at 17:49, =C3=81lvaro Jurado wrot= e: > what ensures sha key is in fs. The reason many of us are a little sceptical about it being fsync as such preventing the data appearing is that if the git function that writes the key does a write or pwrite, the key will be in the file system on Plan 9: there's no need for an fsync just to get it there. In fact, in Linux there's no need for an fsync just to get it there: it only matters in the case of a crash. If the file system fails or you reset the machine, the intention of the fsync will be frustrated, but it shouldn't affect normal operation where no file server crash occurs. As it happens, a wstat that changes nothing can be interpreted by a file server to have a similar effect as fsync (see stat(5)). --001a11c1b90e34c4b10521eb43ef Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On 12 October 2015 at 17:49, =C3=81lvaro Jurado <elbingmiss@gmail.com> wrote:

what ensures sha key= is in fs.

The reason many of us are a little sceptic= al about it being fsync as such preventing the data appearing

is that if the git function that writes the key does a w= rite or pwrite,

the key will be in the file= system on Plan 9: there's no need for an fsync just to get it there.

In fact, in Linux there's no need for an= fsync just to get it there: it only matters in the case of a crash.

<= div class=3D"gmail_extra">

If the file = system fails or you reset the machine, the intention of the fsync will be f= rustrated, but

it shouldn't affect norm= al operation where no file server crash occurs.

As it happens, a wstat that chang= es nothing can be interpreted by a file server to have a similar effect as = fsync (see stat(5)).

--001a11c1b90e34c4b10521eb43ef-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> <9c545c7fbde6ddecb82def2dc66194ed@lilly.quanstro.net>

Date: Mon, 12 Oct 2015 19:54:47 +0200 Message-ID: From: =?UTF-8?Q?=C3=81lvaro_Jurado?= To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a114023186fedde0521ec0673 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 7310383a-ead9-11e9-9d60-3106f5b1d025 --001a114023186fedde0521ec0673 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Has sense. Thanks Charles. =C3=81lvaro El 12/10/2015 19:03, "Charles Forsyth" escribi= =C3=B3: > > On 12 October 2015 at 17:49, =C3=81lvaro Jurado wr= ote: > >> what ensures sha key is in fs. > > > The reason many of us are a little sceptical about it being fsync as such > preventing the data appearing > is that if the git function that writes the key does a write or pwrite, > the key will be in the file system on Plan 9: there's no need for an fsyn= c > just to get it there. > In fact, in Linux there's no need for an fsync just to get it there: it > only matters in the case of a crash. > > If the file system fails or you reset the machine, the intention of the > fsync will be frustrated, but > it shouldn't affect normal operation where no file server crash occurs. > > As it happens, a wstat that changes nothing can be interpreted by a file > server to have a similar effect as fsync (see stat(5)). > --001a114023186fedde0521ec0673 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Has sense. Thanks Charles.

=C3=81lvaro

El 12/10/2015 19:03, "Charles Forsyth"= <charles.forsyth@gmail.com= > escribi=C3=B3:

On 12 October 2015 at 17:49, =C3=81lvaro Jurado <<= a href=3D"mailto:elbingmiss@gmail.com" target=3D"_blank">elbingmiss@gmail.c= om> wrote:
what ensures sha= key is in fs.

The reason many of us are a little sce= ptical about it being fsync as such preventing the data appearing
is that if the git function that writes the key does= a write or pwrite,
the key will be in the = file system on Plan 9: there's no need for an fsync just to get it ther= e.
In fact, in Linux there's no need fo= r an fsync just to get it there: it only matters in the case of a crash.

If the f= ile system fails or you reset the machine, the intention of the fsync will = be frustrated, but
it shouldn't affect = normal operation where no file server crash occurs.

As it happens, a wstat that c= hanges nothing can be interpreted by a file server to have a similar effect= as fsync (see stat(5)).

--001a114023186fedde0521ec0673-- From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <385c85ca703ac8d441c4227d1bb24643@u2.inri> <9c545c7fbde6ddecb82def2dc66194ed@lilly.quanstro.net>

Date: Mon, 12 Oct 2015 22:25:25 +0200 Message-ID: From: Giacomo Tesio To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d04428cc02331c10521ee2128 Subject: Re: [9fans] off topic - a good Git reference Topicbox-Message-UUID: 73220984-ead9-11e9-9d60-3106f5b1d025 --f46d04428cc02331c10521ee2128 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 2015-10-12 19:00 GMT+02:00 Charles Forsyth : > > On 12 October 2015 at 17:49, =C3=81lvaro Jurado wr= ote: > >> what ensures sha key is in fs. > > > The reason many of us are a little sceptical about it being fsync as such > preventing the data appearing > is that if the git function that writes the key does a write or pwrite, > the key will be in the file system on Plan 9: there's no need for an fsyn= c > just to get it there. > In fact, in Linux there's no need for an fsync just to get it there: it > only matters in the case of a crash. > > If the file system fails or you reset the machine, the intention of the > fsync will be frustrated, but > it shouldn't affect normal operation where no file server crash occurs. > > As it happens, a wstat that changes nothing can be interpreted by a file > server to have a similar effect as fsync (see stat(5)). > Thus Plan9 HAS fsync! :-o And it also has server-defined semantics! Very impressive! Giacomo --f46d04428cc02331c10521ee2128 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

2015-10-12 19:00 GMT+02:00 Charles Forsyth <charles.forsyth@gmail.com>:

On 12 October 2015 at 17:49, =C3=81lvaro Jurado <elbingmiss@gmail.com= > wrote:
what ensures sha k= ey is in fs.

The reason many of us are a littl= e sceptical about it being fsync as such preventing the data appearing
is that if the git function that writes the key= does a write or pwrite,
the key will be in= the file system on Plan 9: there's no need for an fsync just to get it= there.
In fact, in Linux there's no ne= ed for an fsync just to get it there: it only matters in the case of a cras= h.

If = the file system fails or you reset the machine, the intention of the fsync = will be frustrated, but
it shouldn't af= fect normal operation where no file server crash occurs.

As it happens, a wstat t= hat changes nothing can be interpreted by a file server to have a similar e= ffect as fsync (see stat(5)).

Thus Plan9 HAS fsync! :-o

And it also= has server-defined semantics! Very impressive!

Giacomo

<= /div>

--f46d04428cc02331c10521ee2128--