All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Oliver Kullmann <O.Kullmann@swansea.ac.uk>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: how to move with history?
Date: Mon, 18 Jun 2007 16:31:16 -0400	[thread overview]
Message-ID: <20070618203116.GK2334@fieldses.org> (raw)
In-Reply-To: <20070618202918.GM3037@cs-wsok.swansea.ac.uk>

On Mon, Jun 18, 2007 at 09:29:18PM +0100, Oliver Kullmann wrote:
> On Mon, Jun 18, 2007 at 09:49:07PM +0200, Alex Riesen wrote:
> > Git does not keep "renaming history". It does not have to, as it keeps
> > how your project looked at each commit (point in history).
> 
> For my purposes, that is a bad thing, since I want to get rid off some parts
> of the history (specifically I want to eliminate some files from history),
> as explained in that last paragraph in my e-mail (with the motivation):

Oh, so even if somebody checks out a previous version of the project,
you don't want them to see that file at the old name any more?

The git history is totally immutable, by design--the SHA1 name of a
commit is taken over the commit, the contents of the entire tree at that
point, and any commit(s) that precede this commit--hence it recursively
summarizes the entire history of the project.

So if you want to erase all memory of a path from the git history, then
you have to rebuild it all.  Which is possible--it'd just mean creating
a new project and writing a script to import every version into the new
project....

--b.

  reply	other threads:[~2007-06-18 20:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 19:16 how to move with history? Oliver Kullmann
2007-06-18 19:49 ` Alex Riesen
2007-06-18 20:29   ` Oliver Kullmann
2007-06-18 20:31     ` J. Bruce Fields [this message]
2007-06-18 20:36       ` Frank Lichtenheld
2007-06-18 20:43     ` Robin Rosenberg
2007-06-18 21:07     ` Alex Riesen
2007-06-19 19:28       ` Oliver Kullmann
2007-06-19 22:59         ` Jakub Narebski

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=20070618203116.GK2334@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=O.Kullmann@swansea.ac.uk \
    --cc=git@vger.kernel.org \
    --cc=raa.lkml@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.