git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: files are disappearing in git
Date: Thu, 24 Nov 2005 09:46:33 +0100	[thread overview]
Message-ID: <20051124084633.GA3361@schottelius.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0511230917130.13959@g5.osdl.org>

[-- Attachment #1: Type: text/plain, Size: 2720 bytes --]

Linus Torvalds [Wed, Nov 23, 2005 at 09:20:28AM -0800]:
> On Wed, 23 Nov 2005, Nico -telmich- Schottelius wrote:
> > 
> > I've the problem that some files (a directory with 3 files) is simply 'away':
> > 
> > - We added it once
> > - In current tree it's away
> > - pasky aided me in irc to find the commit where it is gone with git bisect
> > --> very nice tool
> > - the commit, after which the directory was gone did NOT modify this directory
> > - though the directory is gone
> > 
> > What should I do know to find out what's the reason git 'forgot' that directory?
> 
> I bet somebody just messed up the index before that commit.

What would be the best things to corrupt the index?
Our developers here do the following each day:

- cg-update
- <work>
- cg-commit
- cg-update + merge if there are changes
- cg-push origin
--> this goes to NFS mounted /home (in which developers also work)
[9:34] klapperwachstum:walderlift% cat .git/branches/origin 
/home/server/git/walderlift.git


> So the commit 
> probably _did_ modify the directory, though some incorrect patching or 
> some scripting bug.

Hrm, perhaps this is true, though I am not aware _how_ they (two people
besides me) could even manage to do that. Our developers are
Kylix developers under Linux, who are raelly limited to the above
cg-commands and using gitweb for seeing changes.

> If you can guess at all what went on at around that commit (what else 
> happened there?) that might help.

In this commit where specified three files changed. The commit text is not related
to the directory which is missing.

Files changed are

Code/Components/Utilities/LW1Calendar.pas
Code/lw1/Client/Terminierung/FeinTerminierungForm.pas
Code/lw1/Client/Terminierung/FeinTerminierungForm.xfm

and files missing after this release are

Code/Spikes/Statistik/

If I select "history" of one of the files at the point it still existed in the tree,
it has only one entry, where it was added.

> Was it a merge?

No, we also assumed that first, but git bisect showed that it is not.

> Is the tree public so that we can look at it and perhaps make a guess from 
> what happened around it?

I am sorry it is not. Perhaps I can convince my boss to allow access to it for
some git developers, so someone could debug it. Thought, every information
found in the tree would have to be treated confidental.

Do you have some other hints on how to debug that? Perhaps some conistency checking
tool?

Or perhaps should I put that git directory under cvs? ;-)

Nico

-- 
Latest project: cinit-0.2.1 (http://linux.schottelius.org/cinit/)
Open Source nutures open minds and free, creative developers.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 827 bytes --]

  reply	other threads:[~2005-11-24  8:46 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 [this message]
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
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=20051124084633.GA3361@schottelius.org \
    --to=nico-linux-git@schottelius.org \
    --cc=git@vger.kernel.org \
    --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).