I've started using git fairly heavily (although not necessarily very well). I have several repos: a couple are code, also my ~/.vim/ folder and I'm thinking about adding ~/bin/ . If I remember to push from a particular machine before leaving it, I'll never have to deal with merging as I'm the only user. While most likely my discomfort with merging will be overcome by practice as I understand git does it well (I use SVN at work: merging is shudder-inducing), I'm guessing keeping everything up to date is still preferable. These questions are mostly about incorporating information about the repo into the Bash prompt: I was impressed recently by the way zsh appears to handle it, with a sequence of tiny icons in the lower right corner of the terminal indicating relative status. I didn't talk to the zsh user long, so I don't know if that's built-in, a plugin, or something he did himself. I'm starting from some code I got from nitrous.io, lovely in its conciseness: parse_git_branch () { git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e "s/* \(.*\)/\1$(parse_git_dirty)/" } parse_git_dirty () { git diff --no-ext-diff --quiet --exit-code &>/dev/null || echo "!" } Put \$(parse_git_branch) into your prompt and it tells you what branch you're on, and if there are any unstaged changes (and goes away if you're not in a repo). I'd prefer it did uncommitted rather than unstaged, haven't tried to fix that yet. But I want to update it as it doesn't deal with origin at all. So, the questions: What is the easiest and most concise way to determine if your local is behind origin master? I've found that "git remote show origin" will show this information, but I'm not sure if it's the "best" way to find out, and I'm also concerned that running that every time your prompt comes up would slow things down as it makes a remote call(?) to get an answer - when you might not even have a network connection, or worse, a very slow connection. "git status" usually says "Your branch is up-to-date with 'origin/master'" (or "ahead"), but occasionally - even though origin is configured properly - this line doesn't appear. Is there a way to convince it to always show this line? Unfortunately, "git status" doesn't seem to ever notice if you're "behind" origin, thus the need for "git remote show origin". Any fix for that? The thought was to have output for the prompt that looked like this: (everything synced): "master-" (uncommitted local changes): "master!-" (behind origin): "master^" (ahead of origin): "masterv" (ahead and behind, with local changes): "master!^v" You get the general idea. I'm aware git is capable of immense complexity (branches, detached head, multiple remotes, different remotes for push and pull, etc.) that aren't addressed here. If I tried to tackle all of that at once (especially given I don't understand most of it) my head would explode and nothing would get done. So I'm sticking with my simple use case until I have to deal with the more complex stuff. Any thoughts welcome. -- Giles http://www.gilesorr.com/ gilesorr@gmail.com
Hi Giles, Try installing 'gitk' graphical tool that visualize a lot of things your asking about. Just run "gitk &" from anywhere under your git project root repository. Alex. On Fri, Mar 6, 2015 at 10:29 AM, Giles Orr <gilesorr@gmail.com> wrote:
I've started using git fairly heavily (although not necessarily very well). I have several repos: a couple are code, also my ~/.vim/ folder and I'm thinking about adding ~/bin/ . If I remember to push from a particular machine before leaving it, I'll never have to deal with merging as I'm the only user. While most likely my discomfort with merging will be overcome by practice as I understand git does it well (I use SVN at work: merging is shudder-inducing), I'm guessing keeping everything up to date is still preferable. These questions are mostly about incorporating information about the repo into the Bash prompt: I was impressed recently by the way zsh appears to handle it, with a sequence of tiny icons in the lower right corner of the terminal indicating relative status. I didn't talk to the zsh user long, so I don't know if that's built-in, a plugin, or something he did himself.
I'm starting from some code I got from nitrous.io, lovely in its conciseness:
parse_git_branch () { git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e "s/* \(.*\)/\1$(parse_git_dirty)/" } parse_git_dirty () { git diff --no-ext-diff --quiet --exit-code &>/dev/null || echo "!" }
Put \$(parse_git_branch) into your prompt and it tells you what branch you're on, and if there are any unstaged changes (and goes away if you're not in a repo). I'd prefer it did uncommitted rather than unstaged, haven't tried to fix that yet. But I want to update it as it doesn't deal with origin at all.
So, the questions:
What is the easiest and most concise way to determine if your local is behind origin master? I've found that "git remote show origin" will show this information, but I'm not sure if it's the "best" way to find out, and I'm also concerned that running that every time your prompt comes up would slow things down as it makes a remote call(?) to get an answer - when you might not even have a network connection, or worse, a very slow connection.
"git status" usually says "Your branch is up-to-date with 'origin/master'" (or "ahead"), but occasionally - even though origin is configured properly - this line doesn't appear. Is there a way to convince it to always show this line?
Unfortunately, "git status" doesn't seem to ever notice if you're "behind" origin, thus the need for "git remote show origin". Any fix for that?
The thought was to have output for the prompt that looked like this:
(everything synced): "master-" (uncommitted local changes): "master!-" (behind origin): "master^" (ahead of origin): "masterv" (ahead and behind, with local changes): "master!^v"
You get the general idea.
I'm aware git is capable of immense complexity (branches, detached head, multiple remotes, different remotes for push and pull, etc.) that aren't addressed here. If I tried to tackle all of that at once (especially given I don't understand most of it) my head would explode and nothing would get done. So I'm sticking with my simple use case until I have to deal with the more complex stuff.
Any thoughts welcome.
-- Giles http://www.gilesorr.com/ gilesorr@gmail.com --- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
Hi Alex. I live and die by the command line, and I'm fairly sure all of this can be achieved without installing extra tools (and gitk wouldn't play well with remote servers). I'm hoping to have a quick status update that's always there, no extra commands needed. On 6 March 2015 at 10:40, Alex Volkov <avolkov@gmail.com> wrote:
Try installing 'gitk' graphical tool that visualize a lot of things your asking about. Just run "gitk &" from anywhere under your git project root repository.
Alex.
On Fri, Mar 6, 2015 at 10:29 AM, Giles Orr <gilesorr@gmail.com> wrote:
I've started using git fairly heavily (although not necessarily very well). I have several repos: a couple are code, also my ~/.vim/ folder and I'm thinking about adding ~/bin/ . If I remember to push from a particular machine before leaving it, I'll never have to deal with merging as I'm the only user. While most likely my discomfort with merging will be overcome by practice as I understand git does it well (I use SVN at work: merging is shudder-inducing), I'm guessing keeping everything up to date is still preferable. These questions are mostly about incorporating information about the repo into the Bash prompt: I was impressed recently by the way zsh appears to handle it, with a sequence of tiny icons in the lower right corner of the terminal indicating relative status. I didn't talk to the zsh user long, so I don't know if that's built-in, a plugin, or something he did himself.
I'm starting from some code I got from nitrous.io, lovely in its conciseness:
parse_git_branch () { git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e "s/* \(.*\)/\1$(parse_git_dirty)/" } parse_git_dirty () { git diff --no-ext-diff --quiet --exit-code &>/dev/null || echo "!" }
Put \$(parse_git_branch) into your prompt and it tells you what branch you're on, and if there are any unstaged changes (and goes away if you're not in a repo). I'd prefer it did uncommitted rather than unstaged, haven't tried to fix that yet. But I want to update it as it doesn't deal with origin at all.
So, the questions:
What is the easiest and most concise way to determine if your local is behind origin master? I've found that "git remote show origin" will show this information, but I'm not sure if it's the "best" way to find out, and I'm also concerned that running that every time your prompt comes up would slow things down as it makes a remote call(?) to get an answer - when you might not even have a network connection, or worse, a very slow connection.
"git status" usually says "Your branch is up-to-date with 'origin/master'" (or "ahead"), but occasionally - even though origin is configured properly - this line doesn't appear. Is there a way to convince it to always show this line?
Unfortunately, "git status" doesn't seem to ever notice if you're "behind" origin, thus the need for "git remote show origin". Any fix for that?
The thought was to have output for the prompt that looked like this:
(everything synced): "master-" (uncommitted local changes): "master!-" (behind origin): "master^" (ahead of origin): "masterv" (ahead and behind, with local changes): "master!^v"
You get the general idea.
I'm aware git is capable of immense complexity (branches, detached head, multiple remotes, different remotes for push and pull, etc.) that aren't addressed here. If I tried to tackle all of that at once (especially given I don't understand most of it) my head would explode and nothing would get done. So I'm sticking with my simple use case until I have to deal with the more complex stuff.
Any thoughts welcome.
-- Giles http://www.gilesorr.com/ gilesorr@gmail.com
On Fri 06 Mar 2015 10:52 -0500, Giles Orr wrote:
I live and die by the command line, and I'm fairly sure all of this can be achieved without installing extra tools (and gitk wouldn't play well with remote servers). I'm hoping to have a quick status update that's always there, no extra commands needed.
As far as finding out your status against a remote you will have to use a network connection and query the remote. There's no way around that. You can fetch the remote (git fetch) ahead of time, and I suppose get some reasonable idea of where you stand later. Try tig, a curses based git explorer http://jonas.nitro.dk/tig/ What do you use for mail on the command line?
Seconding TIG, definitely my favourite git viewing tool, command line or otherwise. On Fri, Mar 6, 2015 at 1:24 PM, Loui Chang <louipc.ist@gmail.com> wrote:
On Fri 06 Mar 2015 10:52 -0500, Giles Orr wrote:
I live and die by the command line, and I'm fairly sure all of this can be achieved without installing extra tools (and gitk wouldn't play well with remote servers). I'm hoping to have a quick status update that's always there, no extra commands needed.
As far as finding out your status against a remote you will have to use a network connection and query the remote. There's no way around that. You can fetch the remote (git fetch) ahead of time, and I suppose get some reasonable idea of where you stand later.
Try tig, a curses based git explorer http://jonas.nitro.dk/tig/
What do you use for mail on the command line?
--- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
Most of the GUIs just add a different wodge of complexity, where each is subtly different. From the command-line, an alias or script like git log --oneline --abbrev-commit --all --graph --decorate --color will show you quite enough to make your head hurt, and is what the authoers use. --dave On 03/06/2015 10:40 AM, Alex Volkov wrote:
Hi Giles,
Try installing 'gitk' graphical tool that visualize a lot of things your asking about. Just run "gitk &" from anywhere under your git project root repository.
Alex.
On Fri, Mar 6, 2015 at 10:29 AM, Giles Orr <gilesorr@gmail.com <mailto:gilesorr@gmail.com>> wrote:
I've started using git fairly heavily (although not necessarily very well). I have several repos: a couple are code, also my ~/.vim/ folder and I'm thinking about adding ~/bin/ . If I remember to push from a particular machine before leaving it, I'll never have to deal with merging as I'm the only user. While most likely my discomfort with merging will be overcome by practice as I understand git does it well (I use SVN at work: merging is shudder-inducing), I'm guessing keeping everything up to date is still preferable. These questions are mostly about incorporating information about the repo into the Bash prompt: I was impressed recently by the way zsh appears to handle it, with a sequence of tiny icons in the lower right corner of the terminal indicating relative status. I didn't talk to the zsh user long, so I don't know if that's built-in, a plugin, or something he did himself.
I'm starting from some code I got from nitrous.io <http://nitrous.io>, lovely in its conciseness:
parse_git_branch () { git branch --no-color 2> /dev/null | sed -e '/^[^*]/d' -e "s/* \(.*\)/\1$(parse_git_dirty)/" } parse_git_dirty () { git diff --no-ext-diff --quiet --exit-code &>/dev/null || echo "!" }
Put \$(parse_git_branch) into your prompt and it tells you what branch you're on, and if there are any unstaged changes (and goes away if you're not in a repo). I'd prefer it did uncommitted rather than unstaged, haven't tried to fix that yet. But I want to update it as it doesn't deal with origin at all.
So, the questions:
What is the easiest and most concise way to determine if your local is behind origin master? I've found that "git remote show origin" will show this information, but I'm not sure if it's the "best" way to find out, and I'm also concerned that running that every time your prompt comes up would slow things down as it makes a remote call(?) to get an answer - when you might not even have a network connection, or worse, a very slow connection.
"git status" usually says "Your branch is up-to-date with 'origin/master'" (or "ahead"), but occasionally - even though origin is configured properly - this line doesn't appear. Is there a way to convince it to always show this line?
Unfortunately, "git status" doesn't seem to ever notice if you're "behind" origin, thus the need for "git remote show origin". Any fix for that?
The thought was to have output for the prompt that looked like this:
(everything synced): "master-" (uncommitted local changes): "master!-" (behind origin): "master^" (ahead of origin): "masterv" (ahead and behind, with local changes): "master!^v"
You get the general idea.
I'm aware git is capable of immense complexity (branches, detached head, multiple remotes, different remotes for push and pull, etc.) that aren't addressed here. If I tried to tackle all of that at once (especially given I don't understand most of it) my head would explode and nothing would get done. So I'm sticking with my simple use case until I have to deal with the more complex stuff.
Any thoughts welcome.
-- Giles http://www.gilesorr.com/ gilesorr@gmail.com <mailto:gilesorr@gmail.com> --- Talk Mailing List talk@gtalug.org <mailto:talk@gtalug.org> http://gtalug.org/mailman/listinfo/talk
--- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
-- David Collier-Brown, | Always do right. This will gratify System Programmer and Author | some people and astonish the rest davecb@spamcop.net | -- Mark Twain
Just as an aside, formerly local friend-of-GTALUG Emma Jane Westby is writing a book for O'Reilly called /Git for Teams/. cheers, Stewart
Hi Stewart , Just as an aside, formerly local friend-of-GTALUG Emma Jane Westby is writing a book for O'Reilly called Git for Teams. ---------------------- When she publish it, send us a note. Will pick up one to promote a fellow TLUG William cheers, Stewart
<snip>
Bash prompt: I was impressed recently by the way zsh appears to handle it, with a sequence of tiny icons in the lower right corner of the terminal indicating relative status. I didn't talk to the zsh user long, so I don't know if that's built-in, a plugin, or something he did himself. <snip>
Check this out please : https://github.com/magicmonty/bash-git-prompt This is the zsh one: https://github.com/olivierverdier/zsh-git-prompt Interesting : http://0xfe.blogspot.ca/2010/04/improved-git-enabled-shell-prompt.html Learn Git in 15mins ( Really ! ) : https://try.github.io/levels/1/challenges/1 When all else fails read the documentation luke : http://git-scm.com/book/en/v2 Good Luck :)
I'm a big fan of gitk -- the visual aspect of it appeals to me, as I can see right away where I am, and where the remote branch is. As soon as you do something on the command line, it's reflected in gitk. I'm not a fan of cramming lots of stuff in the command line, but that's a personal preference. Alex On Fri, Mar 6, 2015 at 11:39 AM, Aruna Hewapathirane < aruna.hewapathirane@gmail.com> wrote:
<snip>
Bash prompt: I was impressed recently by the way zsh appears to handle it, with a sequence of tiny icons in the lower right corner of the terminal indicating relative status. I didn't talk to the zsh user long, so I don't know if that's built-in, a plugin, or something he did himself. <snip>
Check this out please : https://github.com/magicmonty/bash-git-prompt
This is the zsh one: https://github.com/olivierverdier/zsh-git-prompt
Interesting : http://0xfe.blogspot.ca/2010/04/improved-git-enabled-shell-prompt.html
Learn Git in 15mins ( Really ! ) : https://try.github.io/levels/1/challenges/1
When all else fails read the documentation luke : http://git-scm.com/book/en/v2
Good Luck :)
--- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
-- Alex Beamish Toronto, Ontario
Thanks, that's great. I think bash-git-prompt will probably be the answer, but the others look very helpful as well. On 6 March 2015 at 11:39, Aruna Hewapathirane <aruna.hewapathirane@gmail.com> wrote:
<snip>
Bash prompt: I was impressed recently by the way zsh appears to handle it, with a sequence of tiny icons in the lower right corner of the terminal indicating relative status. I didn't talk to the zsh user long, so I don't know if that's built-in, a plugin, or something he did himself. <snip>
Check this out please : https://github.com/magicmonty/bash-git-prompt
This is the zsh one: https://github.com/olivierverdier/zsh-git-prompt
Interesting : http://0xfe.blogspot.ca/2010/04/improved-git-enabled-shell-prompt.html
Learn Git in 15mins ( Really ! ) : https://try.github.io/levels/1/challenges/1
When all else fails read the documentation luke : http://git-scm.com/book/en/v2
Good Luck :)
--- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
-- Giles http://www.gilesorr.com/ gilesorr@gmail.com
On 2015-03-06 08:39, Aruna Hewapathirane wrote:
Links: ------ [1] https://github.com/magicmonty/bash-git-prompt [2] https://github.com/olivierverdier/zsh-git-prompt [3] http://0xfe.blogspot.ca/2010/04/improved-git-enabled-shell-prompt.html [4] https://try.github.io/levels/1/challenges/1 [5] http://git-scm.com/book/en/v2
I was forced to start using git as some of the open source projects I work on switched to using it for maintaining their public code repositories. Git is different enough from the other VCS' I have used that it drove me batty at first. With git I often wound up with my checked out code "not on a branch". I've lost code changes I was working on while using git. That never happened while using any of the RCS/CVS/SVN tools. Eventually I started to get a bit of a handle on git and created my own cheat sheet for it. I have made it available via the wiki on my website. The URL is http://www.ve3syb.ca/wiki/doku.php/docs:git_survivors_guide -- Cheers! Kevin. http://www.ve3syb.ca/ |"Nerds make the shiny things that distract Owner of Elecraft K2 #2172 | the mouth-breathers, and that's why we're | powerful!" #include <disclaimer/favourite> | --Chris Hardwick
On Mon, Apr 06, 2015 at 04:16:02PM -0400, Kevin wrote:
On 2015-03-06 08:39, Aruna Hewapathirane wrote:
Links: ------ [1] https://github.com/magicmonty/bash-git-prompt [2] https://github.com/olivierverdier/zsh-git-prompt [3] http://0xfe.blogspot.ca/2010/04/improved-git-enabled-shell-prompt.html [4] https://try.github.io/levels/1/challenges/1 [5] http://git-scm.com/book/en/v2
I was forced to start using git as some of the open source projects I work on switched to using it for maintaining their public code repositories. Git is different enough from the other VCS' I have used that it drove me batty at first. With git I often wound up with my checked out code "not on a branch". I've lost code changes I was working on while using git. That never happened while using any of the RCS/CVS/SVN tools. Eventually I started to get a bit of a handle on git and created my own cheat sheet for it.
And at the same time a lot of people won't contribute to projects because dealing with RCS(ok no one uses that)/CVS/SVN is way too painful. then there is bazaar, which really would be better named bizaar, as far as the UI is concerned. git is different, but it's different in a good way. Now I must admit I have no idea how one can end up not on a branch. I have never managed that as far as I recall. Actually maybe doing a checkout of a specific commit number will do that, but I only ever do that when trying to investigate when something changed, certainly never while writing code.
I have made it available via the wiki on my website. The URL is http://www.ve3syb.ca/wiki/doku.php/docs:git_survivors_guide
-- Len Sorensen
On Fri, Mar 6, 2015 at 10:29 AM, Giles Orr <gilesorr@gmail.com> wrote:
"git status" usually says "Your branch is up-to-date with 'origin/master'" (or "ahead"), but occasionally - even though origin is configured properly - this line doesn't appear. Is there a way to convince it to always show this line?
Unfortunately, "git status" doesn't seem to ever notice if you're "behind" origin, thus the need for "git remote show origin". Any fix for that?
`git status` only looks at what's on your local file system. You need to first do a `git fetch` to update your local information (doesn't change your code, just git's information), then `git status` will reflect what's actually happening. Without some command that fetches things from the remote, `git status` will always say you're up-to-date (or ahead if you've committed things).
About the same time you were sending this, a co-worker was telling me about the virtues of "git fetch" as opposed to "git pull" which I've used almost exclusively. It makes a lot more sense now, thanks. To everyone who answered: I think we can consider my problems (at least the git ones!) solved, and many thanks. On 6 March 2015 at 12:21, Tim Tisdall <tisdall@gmail.com> wrote:
On Fri, Mar 6, 2015 at 10:29 AM, Giles Orr <gilesorr@gmail.com> wrote:
"git status" usually says "Your branch is up-to-date with 'origin/master'" (or "ahead"), but occasionally - even though origin is configured properly - this line doesn't appear. Is there a way to convince it to always show this line?
Unfortunately, "git status" doesn't seem to ever notice if you're "behind" origin, thus the need for "git remote show origin". Any fix for that?
`git status` only looks at what's on your local file system. You need to first do a `git fetch` to update your local information (doesn't change your code, just git's information), then `git status` will reflect what's actually happening. Without some command that fetches things from the remote, `git status` will always say you're up-to-date (or ahead if you've committed things). --- Talk Mailing List talk@gtalug.org http://gtalug.org/mailman/listinfo/talk
-- Giles http://www.gilesorr.com/ gilesorr@gmail.com
On 06/03/15 12:33 PM, Giles Orr wrote:
About the same time you were sending this, a co-worker was telling me about the virtues of "git fetch" as opposed to "git pull" which I've used almost exclusively. It makes a lot more sense now, thanks.
To everyone who answered: I think we can consider my problems (at least the git ones!) solved, and many thanks.
Missed this thread but thought I'd chime in with a plug for Oh My Zsh! I use it with a solarized terminal theme, the git plugin, and a customized prompt to show the git branch that I'm on: export PROMPT="%{$FG[154]%}[%*|%D]% %{$fg[blue]%} %{%}%n%{%}@%{%}%m%{%}:%{$fg[red]%} %~% %{$fg[black]%}>>%k %{$FG[032]%} %B%? %s%%%k %b" function git_prompt_info() { ref=$(git symbolic-ref HEAD 2> /dev/null) || return echo "$ZSH_THEME_GIT_PROMPT_PREFIX${ref#refs/heads/}$ZSH_THEME_GIT_PROMPT_SUFFIX" } The nice thing about it is when something extends across the entirety of the prompt, the (branch-marker) goes away too. I don't pretend to know what 99% of that does because once I got it setup I haven't ever dared fiddle with it :p It doesn't do stuff like show revs ahead/behind or anything, but I'm sure some creative aliases would make that pretty straightforward. Cheers, Jamon
On 10 March 2015 at 17:44, Jamon Camisso <jamon.camisso@utoronto.ca> wrote:
On 06/03/15 12:33 PM, Giles Orr wrote:
About the same time you were sending this, a co-worker was telling me about the virtues of "git fetch" as opposed to "git pull" which I've used almost exclusively. It makes a lot more sense now, thanks.
To everyone who answered: I think we can consider my problems (at least the git ones!) solved, and many thanks.
Missed this thread but thought I'd chime in with a plug for Oh My Zsh! I use it with a solarized terminal theme, the git plugin, and a customized prompt to show the git branch that I'm on:
export PROMPT="%{$FG[154]%}[%*|%D]% %{$fg[blue]%} %{%}%n%{%}@%{%}%m%{%}:%{$fg[red]%} %~% %{$fg[black]%}>>%k %{$FG[032]%} %B%? %s%%%k %b"
function git_prompt_info() { ref=$(git symbolic-ref HEAD 2> /dev/null) || return echo "$ZSH_THEME_GIT_PROMPT_PREFIX${ref#refs/heads/}$ZSH_THEME_GIT_PROMPT_SUFFIX" }
The nice thing about it is when something extends across the entirety of the prompt, the (branch-marker) goes away too.
I don't pretend to know what 99% of that does because once I got it setup I haven't ever dared fiddle with it :p
It doesn't do stuff like show revs ahead/behind or anything, but I'm sure some creative aliases would make that pretty straightforward.
As a follow-up to my part of this thread, a fair bit of research on my part suggests that yes, Oh My Zsh! is kind of the way to go. Although if you want to stay with Bash (and I admit I have a lot of sunk cost there), there's Bash-it ( https://github.com/Bash-it/bash-it ) which is an attempt to replicate OMZ! for Bash. There's also oh-my-git ( https://github.com/arialdomartini/oh-my-git ), a garish but thorough git prompt for zsh or Bash that could act as a base for a less brightly coloured prompt - although it requires modified fonts. As for tracking upstreams, it's looking like the best procedure for me, if I really want to be concerned about that all the time, is to run "git fetch origin <whatever>" by cron: once you have local unmerged copies, git's tools can readily tell you about the state of the upstream without an on-the-instant network connection. Not quite what I'd hoped for, but when I think about how git works, it's an acceptable compromise. -- Giles http://www.gilesorr.com/ gilesorr@gmail.com
participants (13)
-
Alex Beamish -
Alex Volkov -
Aruna Hewapathirane -
David Collier-Brown -
Erich Welz -
Giles Orr -
Jamon Camisso -
Kevin -
Lennart Sorensen -
Loui Chang -
Stewart C. Russell -
Tim Tisdall -
William Muriithi