Hi folks,
in an effort to make Samba development easier, we're trying to merge the=20
Samba3 and Samba4 branches into a single branch. In order to do so, we need=
=20
to rename the "source" directories both Samba 3 and Samba 4 have (we're=20
planning to use source3 and source4).
Unfortunately, the directories are big enough that git log stops to track t=
he=20
renamed files, so e.g. git log ./samba3 does not show the samba3 history. T=
he=20
history is not lost, of course, but it's way less intuitive to get it.
Here's how we merged the two branches:
$ mkdir samba-merged
$ cd samba-merged
$ git init
=2E.. (create COPYING, README and other top-level files, git add them)
$ git commit -m "Initial commit of merged samba"
$ git remote add git://git.samba.org/samba.git samba
$ git remote update
$ cp -a ~/samba3/source source3
$ cp -a ~/samba4/source source4
$ git add source3 source4
$ git write-tree
$ echo "merge branches" | git commit-tree <sha1 git write-tree retured> \
-p <sha1 of the initial commit> \
-p <sha1 of the current samba3 head> \
-p <sha1 of the current samba4 head>
$ git reset --hard <sha1 returned by git commit-tree>
$ git log
=2E.. history is there as expected
$ git log samba3
=2E.. history is just the merge commit
$ git log samba4
=2E.. history is just the merge commit
Is there any way to fix this that doesn't involve changing the history with=
=20
git-filter-branch?
Cheers,
Kai
=2D-=20
Kai Blin
WorldForge developer http://www.worldforge.org/
Wine developer http://wiki.winehq.org/KaiBlin
Samba team member http://www.samba.org/samba/team/
=2D-
Will code for cotton.| Linus Torvalds | Linux 2.6.21 |
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Greg Kroah-Hartman | [PATCH 002/196] Chinese: rephrase English introduction in HOWTO |
git: | |
| Andrew Morton | Re: [Bugme-new] [Bug 12877] New: tg3: eth0 transit timed out, resetting -> dead NIC |
| Krzysztof Oledzki | Error: an inet prefix is expected rather than "0/0". |
| David Miller | Re: iptables very slow after commit784544739a25c30637397ace5489eeb6e15d7d49 |
| Johann Baudy | Packet mmap: TX RING and zero copy |
