From: "Eric Raible" <raible@gmail.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: making a branch with just one file and keeping its whole history
Date: Mon, 21 Jul 2008 11:22:53 -0700 [thread overview]
Message-ID: <279b37b20807211122w3a1e0687wc84693bd95689326@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807211907270.8986@racer>
On Mon, Jul 21, 2008 at 11:08 AM, Johannes Schindelin
<Johannes.Schindelin@gmx.de> wrote:
>
> On Mon, 21 Jul 2008, Eric Raible wrote:
>
>> http://www.gitcasts.com/posts/empty-branches
>
> Beware! This is one of the sites that triggered my mail about considering
> teaching plumbing to new users harmful.
>
> In other words, I think that these "git casts" are not really the best way
> to teach Git to new users, but rather confusing.
>
> Which is a pity, because they are nicely done otherwise.
>
> Ciao,
> Dscho
I understand your concern, but if you treat that particular gitcast
simple as a recipe to be followed it accomplishes the goal in the
in the most straightforward way I've seen.
A new-user pure-porcelain way would be to branch then delete all
of the files in the branch. Which seems a bit dirty to me.
Or is there some more intuitive porcelain-ish way of creating
a new empty branch that I haven't thought of?
- Eric
next prev parent reply other threads:[~2008-07-21 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 4:18 making a branch with just one file and keeping its whole history ncrfgs
2008-07-21 16:19 ` Eric Raible
2008-07-21 18:08 ` Johannes Schindelin
2008-07-21 18:22 ` Eric Raible [this message]
2008-07-21 18:39 ` Johannes Schindelin
2008-07-22 2:14 ` extracting the history of a single file as a new project [Was: Re: making a branch with just one file and keeping its whole] ncrfgs
2008-07-22 6:15 ` Sverre Rabbelier
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=279b37b20807211122w3a1e0687wc84693bd95689326@mail.gmail.com \
--to=raible@gmail.com \
--cc=Johannes.Schindelin@gmx.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).