From: Kai Blin <kai@samba.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Directory renames without breaking git log.
Date: Thu, 4 Sep 2008 22:52:34 +0200 [thread overview]
Message-ID: <200809042252.37329.kai@samba.org> (raw)
In-Reply-To: <7vtzcv1yk8.fsf@gitster.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 1377 bytes --]
On Thursday 04 September 2008 21:49:27 Junio C Hamano wrote:
> > git blame still works, and git log --sparse path/to/file works, of
> > course. --sparse makes giving a path a bit pointless, of course, but we
> > probably can live with that for time being. I'm still open for
> > suggestions, of course. :)
>
> Give both directories, like:
>
> "git log -- newdir olddir"
>
> perhaps?
Better, but really ugly, as we'll have to keep doing this for the rest of the
project's life to get the full history. And while it's all nice and fun for
git log -- source3/configure.in source/configure.in, it's less fun for deeper
paths.
We'll probably end up just doing a git-filter-branch renaming the samba3
source dir source3 from the beginning and the samba4 source dir source4 from
the beginning, and then do the octopus merge. Without any paths changing,
that should probably work. It's a bit annoying to break all external
branches, but we only need to do this once, and people will only need to
git-format-patch and git-am once, and we can provide a step-by-step guide for
this as well.
Thanks for the feedback, though. :)
Cheers,
Kai
--
Kai Blin
WorldForge developer http://www.worldforge.org/
Wine developer http://wiki.winehq.org/KaiBlin
Samba team member http://www.samba.org/samba/team/
--
Will code for cotton.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-09-04 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 21:38 Directory renames without breaking git log Kai Blin
2008-09-04 0:16 ` Tarmigan
[not found] ` <200809040853.36433.kai@samba.org>
2008-09-04 18:35 ` Tarmigan
2008-09-04 19:45 ` Kai Blin
2008-09-04 19:49 ` Junio C Hamano
2008-09-04 20:52 ` Kai Blin [this message]
2008-09-04 22:06 ` Junio C Hamano
2008-09-04 20:41 ` 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=200809042252.37329.kai@samba.org \
--to=kai@samba.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.