All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: "Patrick Neuner - Futureweb.at" <neuner@futureweb.at>
Cc: Andreas Ericsson <ae@op5.se>, Jeff King <peff@peff.net>,
	git@vger.kernel.org, David Aguilar <davvid@gmail.com>
Subject: Re: AW: AW: Parallell Development / Switching to GIT
Date: Thu, 02 Jul 2009 08:20:39 +0200	[thread overview]
Message-ID: <4A4C51B7.7010000@viscovery.net> (raw)
In-Reply-To: <B81058949321C8439B9D742F5F8D8FCA01A75CFA@hpserver.intranet.local>

Patrick Neuner - Futureweb.at schrieb:
> We use the update-hook to check into which branches pushes are allowed per different ssh keys. 
> Now, I wonder how I am able to create branches that are below another branch. 
> 
> Like 
> Refs/heads/master
> Refs/heads/dev
> Refs/heads/dev/featureA
> Refs/heads/dev/featureB
> 
> Instead of
> Refs/heads/featureA
> 
> Anything I tried either results in an error or creates the branch under /refs/heads/. 

You cannot have refs/heads/dev and refs/heads/dev/featureA at the same
time, just like you cannot have a file and a directory with the same name
at the same time. In fact, the refs "database" is implemented as physical
files on the file system.

-- Hannes

  reply	other threads:[~2009-07-02  6:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25  9:52 Parallell Development / Switching to GIT Patrick Neuner
2009-06-25 10:11 ` Andreas Ericsson
2009-06-28 17:51   ` AW: " Patrick Neuner - Futureweb.at
2009-06-28 18:47     ` Jeff King
2009-06-28 20:08       ` AW: " Patrick Neuner - Futureweb.at
2009-06-28 22:33         ` David Aguilar
2009-06-29  8:35         ` AW: " Andreas Ericsson
2009-06-29 16:37           ` Peter Harris
2009-07-02  0:47           ` AW: " Patrick Neuner - Futureweb.at
2009-07-02  6:20             ` Johannes Sixt [this message]
2009-07-02 11:44               ` AW: " Patrick Neuner - Futureweb.at
2009-07-02 11:55                 ` Johannes Sixt
2009-06-30  5:32         ` Jeff King

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=4A4C51B7.7010000@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=ae@op5.se \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=neuner@futureweb.at \
    --cc=peff@peff.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.