From: Hadmut Danisch <hadmut@danisch.de>
To: git@vger.kernel.org
Subject: Why can't git open empty branches ?
Date: Wed, 11 Apr 2012 12:35:23 +0200 [thread overview]
Message-ID: <4F855E6B.4010504@danisch.de> (raw)
Hi,
when creating a new branch in git, it is by default filled with the
contents of the current branch.
Sometimes a new but empty branch is needed. There are plenty of
instructions in the web to achieve this with „dirty tricks”, i.e. fiddle
around with git's internals. Which is poor design.
Why doesn't git's branch command support opening empty branches in a
clean an natural way?
regards
Hadmut
next reply other threads:[~2012-04-11 10:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 10:35 Hadmut Danisch [this message]
2012-04-11 10:59 ` Why can't git open empty branches ? 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
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=4F855E6B.4010504@danisch.de \
--to=hadmut@danisch.de \
--cc=git@vger.kernel.org \
/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).