From: Jakub Narebski <jnareb@gmail.com>
To: Abhijit Bhopatkar <bain@devslashzero.com>
Cc: git <git@vger.kernel.org>, teamgit@googlegroups.com
Subject: Re: [RFC] teamGIT bonjour support
Date: Fri, 28 Aug 2009 03:22:58 -0700 (PDT) [thread overview]
Message-ID: <m3skfckzk1.fsf@localhost.localdomain> (raw)
In-Reply-To: <2fcfa6df0908280002y221a22e6md27db56865472144@mail.gmail.com>
Abhijit Bhopatkar <bain@devslashzero.com> writes:
> So I ask you people, is there a solution already cooking someplace?
> may be something i can integrate with teamGIT? (e.g. bonjour plugin
> for git dameon)
There is gitjour:
http://rubyforge.org/projects/gitjour
http://github.com/chad/gitjour
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-08-28 10:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 7:02 [RFC] teamGIT bonjour support Abhijit Bhopatkar
2009-08-28 8:05 ` John Tapsell
2009-08-28 8:39 ` Abhijit Bhopatkar
2009-08-28 10:06 ` Ben Hoskings
2009-08-28 10:17 ` Ben Hoskings
2009-08-28 10:22 ` Jakub Narebski [this message]
2009-08-28 13:07 ` Abhijit Bhopatkar
2009-11-20 9:05 ` Petr Baudis
2009-11-20 9:12 ` Petr Baudis
2009-11-20 9:49 ` Björn Steinbrink
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=m3skfckzk1.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=bain@devslashzero.com \
--cc=git@vger.kernel.org \
--cc=teamgit@googlegroups.com \
/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).