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: Parallell Development / Switching to GIT
Date: Thu, 02 Jul 2009 13:55:12 +0200 [thread overview]
Message-ID: <4A4CA020.5020108@viscovery.net> (raw)
In-Reply-To: <B81058949321C8439B9D742F5F8D8FCA01A75D15@hpserver.intranet.local>
Please don't top-post on this list.
Patrick Neuner - Futureweb.at schrieb:
>> 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.
>
> 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.
Are you refering to the example line such as
refs/heads/bw/.* linus
? Of course, you can have refs/heads/dev/featureA in your repository (and
the shortened branch name would obviously be "dev/featureA"), but then you
cannot have a branch named "dev", i.e. refs/heads/dev.
I don't see how the cited document would be misleading in this regard.
-- Hannes
next prev parent reply other threads:[~2009-07-02 11:55 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
2009-07-02 11:44 ` AW: " Patrick Neuner - Futureweb.at
2009-07-02 11:55 ` Johannes Sixt [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A4CA020.5020108@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).