From: Steffen Nurpmeso <sdaoden@yandex.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] off topic - a good Git reference
Date: Fri, 2 Oct 2015 17:23:19 +0200 [thread overview]
Message-ID: <20151002152319.PJ7TA0-rH%sdaoden@yandex.com> (raw)
In-Reply-To: <D5BA410F-04FD-4CE2-9E2F-F1EEB5511E28@corpus-callosum.com>
Jeff Sickel <jas@corpus-callosum.com> wrote:
|> On Sep 30, 2015, at 2:59 AM, Charles Forsyth <charles.fo\
|> rsyth@gmail.com> wrote:
|>
|> Here's a small but representative example.
|
|That’s 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
next prev parent reply other threads:[~2015-10-02 15:23 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 16:58 Skip Tavakkolian
2015-09-29 17:18 ` Tiago Natel
2015-09-29 19:42 ` Kurt H Maier
2015-09-30 3:11 ` erik quanstrom
2015-09-30 7:18 ` Charles Forsyth
2015-09-30 7:36 ` hiro
2015-09-30 7:47 ` Charles Forsyth
2015-09-30 7:59 ` Charles Forsyth
2015-10-01 17:31 ` Jeff Sickel
2015-10-01 17:38 ` Charles Forsyth
2015-10-01 17:38 ` Ryan Gonzalez
2015-10-01 17:47 ` arnold
2015-10-02 8:32 ` hiro
2015-10-02 8:57 ` Aram Hăvărneanu
2015-10-02 13:10 ` Joseph Stewart
2015-10-02 14:07 ` a.regenfuss
2015-10-02 14:10 ` Aram Hăvărneanu
2015-10-02 21:56 ` a.regenfuss
2015-10-03 1:43 ` Kurt H Maier
2015-10-03 2:30 ` erik quanstrom
2015-10-03 4:37 ` Nick Owens
2015-10-02 15:51 ` lucio
2015-10-02 21:43 ` a.regenfuss
2015-10-02 19:27 ` Steve Simon
2015-10-02 15:23 ` Steffen Nurpmeso [this message]
2015-09-30 8:15 ` lucio
2015-09-30 8:25 ` hiro
2015-09-30 7:43 ` Ori Bernstein
2015-09-30 8:22 ` lucio
2015-09-30 7:43 ` lucio
2015-09-30 10:01 ` Brantley Coile
2015-09-30 10:08 ` Steve Simon
2015-10-03 3:00 ` erik quanstrom
2015-10-01 13:54 ` Prof Brucee
2015-09-30 8:15 ` lego12239
2015-10-03 4:48 erik quanstrom
2015-10-03 5:03 ` Andrew Simmons
2015-10-03 5:19 ` Jacob Todd
2015-10-03 19:26 ` Jeff Sickel
2015-10-03 19:57 ` Jacob Todd
2015-10-05 4:24 ` Prof Brucee
2015-10-07 2:37 sl
2015-10-07 15:17 ` Álvaro Jurado
2015-10-07 16:24 ` Charles Forsyth
2015-10-07 21:23 ` Álvaro Jurado
2015-10-10 15:23 ` erik quanstrom
2015-10-12 11:37 ` Steffen Nurpmeso
2015-10-10 15:26 ` erik quanstrom
2015-10-10 18:25 ` Álvaro Jurado
2015-10-12 11:47 ` Charles Forsyth
2015-10-12 16:49 ` Álvaro Jurado
2015-10-12 17:00 ` Charles Forsyth
2015-10-12 17:54 ` Álvaro Jurado
2015-10-12 20:25 ` Giacomo Tesio
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151002152319.PJ7TA0-rH%sdaoden@yandex.com \
--to=sdaoden@yandex.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).