git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Rabbelier" <alturin@gmail.com>
To: ncrfgs@tin.it, "Junio C Hamano" <gitster@pobox.com>,
	"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, madewokherd@gmail.com
Subject: Re: extracting the history of a single file as a new project [Was: Re: making a branch with just one file and keeping its whole]
Date: Tue, 22 Jul 2008 08:15:57 +0200	[thread overview]
Message-ID: <bd6139dc0807212315j4d1f1ff7rcc92077a8c70dba7@mail.gmail.com> (raw)
In-Reply-To: <20080722041457.52120c2f@mail.tin.it>

On Tue, Jul 22, 2008 at 4:14 AM,  <ncrfgs@tin.it> wrote:
> Let's say we are at commit #3000, I have this content I want to start a
> new project from, which has been put in three different files:
>
> path1/filename1 from commit 1 to commit 1000
> path2/filename1 from commit 1001 to commit 2000
> path2/filename2 from commit 2001 to commit 3000
>
> In the meanwhile path1/filename1 has been created on commit 2500 with
> path1/filename1 having nothing to do with the new project I'd like to
> start.

<snip>

> My first idea to accomplish what I'd like to do, was to use the ouput of
> `git-log -p --follow path2/filename2` with another git command; on
> #git@freenode I've been suggested to use git-clone and
> git-filter-branch.
>

It would seem that this is a valid use-case for a properly working
"git log --follow", yes?

-- 
Cheers,

Sverre Rabbelier

      reply	other threads:[~2008-07-22  6:16 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
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 [this message]

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=bd6139dc0807212315j4d1f1ff7rcc92077a8c70dba7@mail.gmail.com \
    --to=alturin@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=madewokherd@gmail.com \
    --cc=ncrfgs@tin.it \
    --cc=sverre@rabbelier.nl \
    /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).