git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Hadmut Danisch <hadmut@danisch.de>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: Why can't git open empty branches ?
Date: Wed, 11 Apr 2012 14:19:52 +0200	[thread overview]
Message-ID: <vpqbomyv4t3.fsf@bauges.imag.fr> (raw)
In-Reply-To: <4F856F67.4000609@danisch.de> (Hadmut Danisch's message of "Wed, 11 Apr 2012 13:47:51 +0200")

Hadmut Danisch <hadmut@danisch.de> writes:

> e.g. open source software and the web pages describing it (like in git
> hub), or a web server tree and the software generating it. They are
> related, but do not logically share a history.

In these cases, you'll want to have two working directories, if only to
avoid:

git checkout documentation
# fix a typo
git commit
git checkout code
make
# complete rebuild triggered.

> 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,

Not necessarily. I don't see an option in "git init" to change the
default branch name, but you can

git init foo
cd foo
git checkout -b whatever-branch-name

and work.

Otherwise, you can have a branch that is locally called "master", and
push it as another name (but that is probably the "error prone" in your
message ;-) ).

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  parent reply	other threads:[~2012-04-11 12:20 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 [this message]
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=vpqbomyv4t3.fsf@bauges.imag.fr \
    --to=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).