From: Holger Hellmuth <hellmuth@ira.uka.de>
To: Hadmut Danisch <hadmut@danisch.de>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Jonathan Nieder <jrnieder@gmail.com>,
git@vger.kernel.org
Subject: Re: Why can't git open empty branches ?
Date: Wed, 11 Apr 2012 16:16:37 +0200 [thread overview]
Message-ID: <4F859245.908@ira.uka.de> (raw)
In-Reply-To: <4F856F67.4000609@danisch.de>
Hi Hadmut ;-)
On 11.04.2012 13:47, Hadmut Danisch wrote:
> Creating independent branches by pushing two separates into a single
> remote bare is a nice idea, but if I understood git correctly, the very
> first commit in a repos is always to the master branch, where you have
AFAIK the only thing that makes master the initial branch is the file
.git/HEAD that points to master after you "git init". This is not hardcoded.
> So your proposal might work perfectly, but in my eyes it is error
> prone and not user friendly.
Serious errors should not happen since the bare repo on the server is
created with the flag denyNonFastForwards. So even if you had a master
branch in both repos, only one of them, the first one, would succeed in
pushing to the server, a push of the second one would give you an error
message. Maybe not user friendly, but safe.
prev parent reply other threads:[~2012-04-11 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 10:35 Why can't git open empty branches ? Hadmut Danisch
2012-04-11 10:59 ` Jonathan Nieder
2012-04-11 11:06 ` Hadmut Danisch
2012-04-11 11:21 ` Matthieu Moy
2012-04-11 11:47 ` Hadmut Danisch
2012-04-11 12:19 ` Jonathan Nieder
2012-04-11 12:19 ` Matthieu Moy
2012-04-11 14:16 ` Holger Hellmuth [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=4F859245.908@ira.uka.de \
--to=hellmuth@ira.uka.de \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=hadmut@danisch.de \
--cc=jrnieder@gmail.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).