Hi, ok, I see, well then this howto (at the end of page) seems to be misleading. http://www.kernel.org/pub/software/scm/git/docs/howto/update-hook-example.txt as it actually works with the update hook, but not with git itself. Well, anyway, no problem, we will do it different. Thanks Patrick Neuner Futureweb.at Innsbrucker Str. 4 6380 St. Johann neuner@xxxxxxxxxxxx www.futureweb.at Fon: +43 (0) 5352 65335 Fax: +43 (0) 5352 63148 Gratis über Skype anrufen | Skype-ID: futureweb > -----Ursprüngliche Nachricht----- > Von: Johannes Sixt [mailto:j.sixt@xxxxxxxxxxxxx] > Gesendet: Donnerstag, 02. Juli 2009 08:21 > An: Patrick Neuner - Futureweb.at > Cc: Andreas Ericsson; Jeff King; git@xxxxxxxxxxxxxxx; David Aguilar > Betreff: Re: AW: AW: Parallell Development / Switching to GIT > > 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 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html