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 15:30:41 -0500	[thread overview]
Message-ID: <AAEEE224-9335-4B1D-A7C5-BD50B835EC55@corpus-callosum.com> (raw)
In-Reply-To: <CAJSxfmJwHfYq-m=9kUPfzfamfCTV5p0Jy3Jj2yuy1wTFHWA+dg@mail.gmail.com>

You can pick up a Cheesehead hat in Wisconsin, or online…
Some groups I’ve worked with would pass the Cheesehead hat to the person
who checked something in that broke the nightly build.  I’m not saying
being sainted by the 9fans community wouldn’t be an honor, but the
recipient might get something more along the lines of a cheesehead hat.


Until then, you can install hg-git for your python2.7 environment on Plan 9:

mkdir -p $home/lib/python2.7/site-packages/docs
bind -bc $home/lib/python2.7/site-packages /$cputype/lib/python2.7/site-packages
bind -bc $home/lib/python2.7/site-packages /sys/lib/python2.7/site-packages 

Grab dulwich (https://pypi.python.org/pypi/dulwich), I pulled the latest master
from github:

% unzip -f dulwich-master.zip
% cd dulwich

To accommodate a strange import error not setting has_mmap correctly, patch
dulwich/pack.py (this is from my hg clone version after installing):

% hg diff -g dulwich/pack.py
diff --git a/dulwich/pack.py b/dulwich/pack.py
--- a/dulwich/pack.py
+++ b/dulwich/pack.py
@@ -59,6 +59,10 @@
     SEEK_CUR,
     SEEK_END,
     )
+# For some reason the above try, except fails to set has_mmap = False
+if os.uname()[0] == 'Plan9':
+    has_mmap = False
+
 import struct
 from struct import unpack_from
 import zlib


Install dulwich:

% python setup.py --pure install


Grab and install hg-git:

% hg clone https://bitbucket.org/durin42/hg-git
% cd hg-git
% python setup.py install


Add ‘hggit =‘ to your $home/lib/hgrc [extensions].

Test it out:

% hg clone git://github.com/schacon/hg-git.git


It isn’t exactly fast, and there are some cases where cloning using https:// instead
of git:// can be an issue, but it works as a brace|cudgel|kludge until a cleaned up
git is made available for Plan 9.

Now to finish a little transmogrifier git script to trick go get...

-jas



> On Mar 19, 2015, at 1:03 PM, Skip Tavakkolian <skip.tavakkolian@gmail.com> wrote:
> 
> a 9fan/git-fan should volunteer to take one for the team,  learn git thoroughly, then hide it behind an fs layer. we will revere such a person, and nominate him/her for sainthood.
> 
> On Thu, Mar 19, 2015 at 9:35 AM Charles Forsyth <charles.forsyth@gmail.com> wrote:
> 
> On 19 March 2015 at 16:09, <arnold@skeeve.com> wrote:
> There is definitely some
> learning curve and mindset change
> 
> Just what I want from a little servant that's supposed to help me manage some file changes.




  reply	other threads:[~2015-03-19 20:30 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 [this message]
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
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=AAEEE224-9335-4B1D-A7C5-BD50B835EC55@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).