git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Björn Steinbrink" <B.Steinbrink@gmx.de>
To: Petr Baudis <pasky@suse.cz>
Cc: Abhijit Bhopatkar <bain@devslashzero.com>,
	git <git@vger.kernel.org>,
	teamgit@googlegroups.com
Subject: Re: [RFC] teamGIT bonjour support
Date: Fri, 20 Nov 2009 10:49:32 +0100	[thread overview]
Message-ID: <20091120094932.GA3528@atjola.homenet> (raw)
In-Reply-To: <20091120091209.GN17748@machine.or.cz>

On 2009.11.20 10:12:09 +0100, Petr Baudis wrote:
> On Fri, Nov 20, 2009 at 10:05:30AM +0100, Petr Baudis wrote:
> >   Hi!
> > 
> > On Fri, Aug 28, 2009 at 12:32:39PM +0530, Abhijit Bhopatkar wrote:
> > > I plan to do this on LAN using bonjour service discovery
> > 
> > I wonder why so much emphasis for this? It seems like a nifty
> > convenience bit, but I don't think making this idea too central is any
> > good. What if you get a second office at the other end of the world?
> > What if part of your team is working on a deployment at customer site?
> > What if part of your team works from home over a VPN?  What if your
> > team is collaborating over the internet on an open project?  What if...?
> > 
> > That said, it sounds like a great idea to have let's say a post-commit
> > hook that will start an upload job:
> > 
> > 	extbranch="$(whoami)/$(git symbolic-ref HEAD | sed 's#refs/heads/##')"
> 
> Thanks to sitaram, now I know that probably the best way is:
> 
>   	extbranch="$(whoami)/$(git describe --contains --all HEAD)"
> 	
> (But now you *really* need to check if HEAD is a heads ref first or you
> will push out to something totally bogus.)

Hm, I'd go for:
$(whoami)/$(git rev-parse --symbolic-full-name HEAD | sed s,refs/heads/,,)

gives the shortname of the checked out branch head, or HEAD when you're
on a detached HEAD.

Bjoern ;-)

      reply	other threads:[~2009-11-20  9:49 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
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 [this message]

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=20091120094932.GA3528@atjola.homenet \
    --to=b.steinbrink@gmx.de \
    --cc=bain@devslashzero.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    --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).