From: Jonathan Nieder <jrnieder@gmail.com>
To: Hadmut Danisch <hadmut@danisch.de>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git@vger.kernel.org
Subject: Re: Why can't git open empty branches ?
Date: Wed, 11 Apr 2012 07:19:07 -0500 [thread overview]
Message-ID: <20120411121907.GA30340@burratino> (raw)
In-Reply-To: <4F856F67.4000609@danisch.de>
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
> two masters trying to push into the shared remote bare. This is
> obviously solvable if you use the correct commands and maybe delete and
> re-clone the repos, but this is all overcomplicated and non-trivial.
> Nothing I could do without reading manuals.
I suppose you had to read the manual to learn the "git commit" and
"git branch -m" commands, yes. But what's wrong with that, or how
could we fix it?
git init code
cd code
... hack away ...
git remote add origin <url>
git push -u origin master
cd ..
git init website
cd website
... hack away ...
git branch -m website
git remote add origin <url>
git push -u origin website
cd ..
I wonder if there is a potential documentation or error message update
lurking behind these questions.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2012-04-11 12:19 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 [this message]
2012-04-11 12:19 ` Matthieu Moy
2012-04-11 14:16 ` Holger Hellmuth
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=20120411121907.GA30340@burratino \
--to=jrnieder@gmail.com \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=hadmut@danisch.de \
/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).