Re: [9fans] Very old bug in db(1)

2015-03-19 Thread Giacomo Tesio
I could be wrong, but looks like nobody cares about such small fixes. A few days ago, I've found some very old small errors (one in the 2c(1) man page and one in col(1) that affects man pages' visualization in variable width fonts) but had no feedback. I guess that the most effective way to cope w

Re: [9fans] Very old bug in db(1)

2015-03-19 Thread lucio
> I guess that the most effective way to cope with such old and small bugs, > is to report them on 9fans (and other related mailing lists), possibly with > a patch. Have checked the man pages for patch(1)? That's the formal procedure; this is a small community so raising your hopes is simply not

Re: [9fans] plan 9 file

2015-03-19 Thread Adrian Regenfuss
I know, I was just interested, because this file contained a lot of [^a-zA-Z]. Thanks for your answer. Adrian Gesendet: Mittwoch, 18. März 2015 um 23:48 Uhr Von: "Ryan Gonzalez" An: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net> Betreff: Re: [9fans] plan 9 file The file command jus

Re: [9fans] Very old bug in db(1)

2015-03-19 Thread Giacomo Tesio
Oh, I completely missed patch(1). And actually it was just when one should look up for at first... man pages. Sorry. Thanks for the tip! It's a fragmented small community and that is just sad. It is not > likely that things will get better in the foreseeable future, so pick > your side :-) To

Re: [9fans] Very old bug in db(1)

2015-03-19 Thread lucio
> It's very hard to find clear statements about the differences between the > various plan9 flavours, or clear descriptions of the vision driving the > development of each fork (at least I wasn't able to find them). I suspect a lot went on in IRC because I've been around this mailing list for deca

Re: [9fans] Very old bug in db(1)

2015-03-19 Thread cinap_lenrek
good catch, thanks :) -- cinap

Re: [9fans] ken cc for linux

2015-03-19 Thread Jeff Sickel
> On Mar 13, 2015, at 1:19 PM, Kurt H Maier wrote: > > github One of these days I’ll get back to finishing the hg-git module for Plan 9. I wish it weren’t required, but as the world has moved to git either git needs to run on Plan 9 or we get the hg-git plugin working and a stub to let go use

[9fans] using git

2015-03-19 Thread arnold
Changed the subject line. Jeff Sickel wrote: > Alas, having git on Plan 9 may not be all that useful for me as git is > the first revision control tool I’ve used where the commands and overall > structure begs for a GUI to make sense of it all. I guess that’s what all > the web interfaces and f

Re: [9fans] using git

2015-03-19 Thread Stanley Lieber
> I'll be happy to continue a > discussion with you offline, if you > wish. are you asking him to take it outside

Re: [9fans] using git

2015-03-19 Thread Charles Forsyth
On 19 March 2015 at 16:09, 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.

Re: [9fans] using git

2015-03-19 Thread Charles Forsyth
Anyway, I moved all my Google Code stuff to mercurial at Bitbucket. I find both the command and web interfaces less annoying and less error-prone.

Re: [9fans] using git

2015-03-19 Thread Federico Benavento
Same here, https://bitbucket.org/fgb/mac9p — Federico Benavento benave...@gmail.com > On Mar 19, 2015, at 1:36 PM, Charles Forsyth > wrote: > > Anyway, I moved all my Google Code stuff to mercurial at Bitbucket. > I find both the command and web interfaces l

Re: [9fans] using git

2015-03-19 Thread Jeff Sickel
> On Mar 19, 2015, at 11:09 AM, arn...@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 sinc

Re: [9fans] using git

2015-03-19 Thread Ori Bernstein
In the past, I have managed to get git-hg to work, but it's been extremely flaky -- for example, Python would refuse to find modules unless I ran hg from within the modules directory. Unfortunately, I've lost the drive with that system since. On Mar 19, 2015, at 10:00 AM, Jeff Sickel wrote: >

Re: [9fans] using git

2015-03-19 Thread Skip Tavakkolian
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 wrote: > > On 19 March 2015 at 16:09, wrote: > >> There is definite

Re: [9fans] using git

2015-03-19 Thread arnold
Charles Forsyth wrote: > On 19 March 2015 at 16:09, 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. Git is intended for something completely different than RCS. I reall

Re: [9fans] using git

2015-03-19 Thread Jeff Sickel
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

Re: [9fans] using git

2015-03-19 Thread Skip Tavakkolian
cool! just to formalize the 9fans steps of canonization, i think it goes something like this: servant of 9fans → loathed → cursed → saint On Thu, Mar 19, 2015 at 1:31 PM Jeff Sickel wrote: > You can pick up a Cheesehead hat in Wisconsin, or online… > Some groups I’ve worked with would pass th

Re: [9fans] using git

2015-03-19 Thread Devon H. O'Dell
2015-03-19 14:46 GMT-07:00 Skip Tavakkolian : > servant of 9fans → loathed → cursed → saint It can (as is probably true in my case) also just stop at either loathed or cursed.

Re: [9fans] using git

2015-03-19 Thread Kurt H Maier
Quoting "Devon H. O'Dell" : 2015-03-19 14:46 GMT-07:00 Skip Tavakkolian : servant of 9fans → loathed → cursed → saint It can (as is probably true in my case) also just stop at either loathed or cursed. You can skip steps, too! Non serviam. khm