From: Eric Raible <raible@gmail.com>
To: git@vger.kernel.org
Subject: Re: making a branch with just one file and keeping its whole history
Date: Mon, 21 Jul 2008 16:19:55 +0000 (UTC) [thread overview]
Message-ID: <loom.20080721T161926-61@post.gmane.org> (raw)
In-Reply-To: 20080721061804.223f7801@mail.tin.it
<ncrfgs <at> tin.it> writes:
>
> Hi,
>
> I have a working local repository and I'd like to make a branch with just one
> file (let's say path2/filename2) and to keep its whole history.
http://www.gitcasts.com/posts/empty-branches
- Eric
next prev parent reply other threads:[~2008-07-21 16:21 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 [this message]
2008-07-21 18:08 ` Johannes Schindelin
2008-07-21 18:22 ` Eric Raible
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=loom.20080721T161926-61@post.gmane.org \
--to=raible@gmail.com \
--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).