Re: as promised, docs: git for the confused
- From
- Josef Weidendorfer <josef.weidendorfer@gmx.de>
- Date
- Dec 9, 2005, 01:19 UTC
- Message-ID
- <200512090219.38297.Josef.Weidendorfer@gmx.de>
- In-Reply-To
- <20051208063409.31967.qmail@science.horizon.com>
On Thursday 08 December 2005 07:34, you wrote:
> As I mentioned with all my questions, I was writing up the answers > I got. Here's the current status. If anyone would like to comment on > its accuracy or usefulness, feedback is appreciated. > ...
Show 12 quoted lines
> + Oddballs > git-mv.perl > I have to admit, I'm not quite sure what advantages this is > supposed to have over plain "mv" followed by "git-update-index", > or why it's complex enough to need perl. > > Basically, this renames a file, deleting its old name and adding > its new name to the index. Otherwise, it's a two-step process > to rename a file: > - Rename the file > - git-add the new name > Followed by which you must commit both the old and new names
The nice thing about it is that you can move huge directories around, or multiple files/dirs at once, and it will do the right thing. E.g. git-mv -k foo* bar/ will only move files which are version controlled.
It is actually a 3-step process: rename, delete old, add new. Perhaps it should be noted that this has nothing to do with any explicit renaming feature like in other SCMs.
Josef