From: Ryan Anderson <ryan@michonline.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>,
Git ML <git@vger.kernel.org>, Petr Baudis <pasky@suse.cz>
Subject: Re: files are disappearing in git
Date: Fri, 25 Nov 2005 14:51:22 -0500 [thread overview]
Message-ID: <20051125195121.GG16995@mythryan2.michonline.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0511251022360.13959@g5.osdl.org>
On Fri, Nov 25, 2005 at 11:12:00AM -0800, Linus Torvalds wrote:
>
> Ok,
>
> Nico gave me private access to the tree, so I quickly cloned it and
> started bisecting it to figure out where the problem was. I haven't looked
> at the source code, and all the commit messages seem to be in German
> (which I can kind of understand if I work at it, but not very well), but
> it definitely turns out none of that matters.
>
> The problem is a bad merge. And in fact, that merge lost _more_ than just
> the three files under Code/Spikes/Statistik/, it also lost a file called
> Code/lw1/Client/Pics/icon/lw1-icon.png.
>
> I don't quite see _how_ it lost them. The merge in question is a totally
> trivial in-index merge, and when I re-do it, I don't lose those files. In
> this case, all the lost files were from the "other branch" of the merge,
> and they were new to that branch. IOW, in git-merge-one-file parlance, it
> is that trivial "added in one" case.
Can something like this sequence do it?
git-init-db
git add file1 ; git commit -m "1"
(cd .. ; git clone tree1 tree2 )
(cd .. ; git clone tree1 tree3 )
git add file2 ; git commit -m "2"
git push ../tree2/
git add file3 ; git commit -m "3"
cd ../tree3/
git add file4
git commit -m "4"
cd ../tree2/
git pull ../tree3/
The key point being that the merge is done in a tree that has its index
out of sync with its HEAD (git push ../tree2/ .... git pull ../tree3/ )
I think that's the situation where I've personally managed to lose
and/or revert some changes.
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2005-11-25 19:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 14:23 files are disappearing in git Nico -telmich- Schottelius
2005-11-23 17:20 ` Linus Torvalds
2005-11-24 8:46 ` Nico -telmich- Schottelius
2005-11-24 9:15 ` Junio C Hamano
2005-11-24 10:38 ` Nico -telmich- Schottelius
2005-11-25 1:54 ` Ryan Anderson
2005-11-25 10:30 ` Nico -telmich- Schottelius
2005-11-25 19:12 ` Linus Torvalds
2005-11-25 19:39 ` Petr Baudis
2005-11-25 19:51 ` Ryan Anderson [this message]
2005-11-25 21:28 ` Junio C Hamano
2005-11-25 22:11 ` Linus Torvalds
2005-11-25 22:48 ` Petr Baudis
2005-11-25 21:28 ` Nico -telmich- Schottelius
2005-11-25 22:57 ` Petr Baudis
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=20051125195121.GG16995@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=git@vger.kernel.org \
--cc=nico-linux-git@schottelius.org \
--cc=pasky@suse.cz \
--cc=torvalds@osdl.org \
/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).