From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
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 22:43:26 +0200 [thread overview]
Message-ID: <200706182243.27068.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20070618202918.GM3037@cs-wsok.swansea.ac.uk>
måndag 18 juni 2007 skrev Oliver Kullmann:
> > 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):
>
> Is this possible in git?
>
> And is it possible to add the history of some file to the history
> of another file (in the above application this would be the renamed
> file) ?
Git does not keep file histories at all. As a consequence it does not track renames
either.
The history in Git is the history of the *whole* tree as a chunk, not a sum of file histories.
It takes snapshots of your project, that's all. Then there are tools to do magic on top of
that (e.g. git-blame).
There are tools to rewrite histories, but then you are violating of
the key principles of git, that history is immutable so git may not be nice to
you after history rewriting. Cogito has a powerful command.
-- robin
next prev parent reply other threads:[~2007-06-18 20:42 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
2007-06-18 20:36 ` Frank Lichtenheld
2007-06-18 20:43 ` Robin Rosenberg [this message]
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=200706182243.27068.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--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 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).