9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] using git
Date: Thu, 19 Mar 2015 12:00:13 -0500	[thread overview]
Message-ID: <45675E46-C464-409B-B75D-DC4C2A3D50AC@corpus-callosum.com> (raw)
In-Reply-To: <201503191609.t2JG9KwH011496@freefriends.org>


> On Mar 19, 2015, at 11:09 AM, arnold@skeeve.com wrote:
> 
> I know some real git fanatics. I'm not one, but I am a "fan". :-)
> 
> I'll be happy to continue a discussion with you offline, if you wish.


Don’t worry Arnold, I’ve been using source control systems for decades and have
used git since the early days.  I’m glad it finally dropped the 'git-pull’ syntax
for the cleaner (clearer|easier ?) to type ‘git pull’ implementation.  If git is
the only DVCS tool you’ve used it wouldn’t hurt giving darcs or hg a cursory review
to gain an understanding of alternative ways to slice the pie.

That said, James did have an early port of hg-git and I’ve gotten close to getting
a new version working with the Python 2.7.x build.  Uriel left git 1.5.6 in his
contrib built for 386.  Unfortunately, Uriel didn’t leave build or install instruction
and his version is highly dependent on APE with all the whacked sh and perl scripts of 
git-wrappers needing to go in /usr/glenda/share/git-core/templates or somewhere, so
I’ve never used it.

If someone were to take on a fresh git port, it should definitely include a mkfile
because that git/git/Makefile will take too long to parse and sort out the mess to
get everything up and running on Plan 9.

-jas




  parent reply	other threads:[~2015-03-19 17:00 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 20:30 [9fans] ken cc for linux Aharon Robbins
2015-03-11 20:34 ` Aram Hăvărneanu
2015-03-11 21:04 ` Ryan Gonzalez
2015-03-11 21:54   ` Quintile
2015-03-11 23:04     ` Ryan Gonzalez
2015-03-11 23:19       ` Steve Simon
2015-03-12  6:39         ` arnold
2015-03-13  1:31     ` erik quanstrom
2015-03-13 13:24       ` Charles Forsyth
2015-03-13 17:59         ` Ryan Gonzalez
2015-03-13 18:19           ` Kurt H Maier
2015-03-19 15:35             ` Jeff Sickel
2015-03-19 16:09               ` [9fans] using git arnold
2015-03-19 16:22                 ` Stanley Lieber
2015-03-19 16:34                 ` Charles Forsyth
2015-03-19 16:36                   ` Charles Forsyth
2015-03-19 16:39                     ` Federico Benavento
2015-04-03 18:46                       ` Jeff Sickel
2015-03-19 18:03                   ` Skip Tavakkolian
2015-03-19 20:30                     ` Jeff Sickel
2015-03-19 21:46                       ` Skip Tavakkolian
2015-03-19 21:54                         ` Devon H. O'Dell
2015-03-20  1:02                           ` Kurt H Maier
2015-03-19 18:26                   ` arnold
2015-03-28 11:14                     ` Charles Forsyth
2015-03-28 14:00                       ` Paul Lalonde
2015-03-30  9:48                         ` Giacomo Tesio
2015-03-30  9:55                           ` Giacomo Tesio
2015-03-30 16:16                             ` Jeff Sickel
2015-03-30 19:47                               ` Stanley Lieber
2015-03-30 20:41                                 ` Bakul Shah
2015-03-30 20:20                               ` Giacomo Tesio
2015-03-30 20:32                                 ` Ryan Gonzalez
2015-03-31  3:17                                 ` arnold
2015-03-19 17:00                 ` Jeff Sickel [this message]
2015-03-19 17:36                   ` Ori Bernstein
2015-03-12  8:50   ` [9fans] ken cc for linux Aram Hăvărneanu
2015-03-12 17:53     ` Ryan Gonzalez
2015-03-12  8:51   ` Aram Hăvărneanu
2015-03-12 10:06     ` Charles Forsyth
2015-03-12 15:23       ` Charles Forsyth
2015-03-12 15:41         ` Brantley Coile
2015-03-12 17:14           ` Charles Forsyth
2015-03-13  1:28             ` erik quanstrom
2015-03-12 17:52     ` Ryan Gonzalez

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=45675E46-C464-409B-B75D-DC4C2A3D50AC@corpus-callosum.com \
    --to=jas@corpus-callosum.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).