git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan Anderson <ryan@michonline.com>
To: Nico -telmich- Schottelius <nico-linux-git@schottelius.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Git ML <git@vger.kernel.org>
Subject: Re: files are disappearing in git
Date: Thu, 24 Nov 2005 20:54:34 -0500	[thread overview]
Message-ID: <43866EDA.9050203@michonline.com> (raw)
In-Reply-To: <20051124084633.GA3361@schottelius.org>

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

Nico -telmich- Schottelius wrote:
> Linus Torvalds [Wed, Nov 23, 2005 at 09:20:28AM -0800]:
 >>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? ;-)

Is there anything in the directory structure that would be confidential?

Can you maybe provide the output of "git-whatchanged" (with no
parameters) or maybe

	git-whatchanged $commit1..$commit2 path/

Where $commit1 is a few commits before the problem, and $commit2 is a
few after it, and path/ is a path above the problem path?

You might add -m to that command line, too.

If the output of one of those commands, which will be commit objects +
tree differences, is less problematic, perhaps that would be easier to
share?




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  parent reply	other threads:[~2005-11-25  1:55 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 [this message]
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=43866EDA.9050203@michonline.com \
    --to=ryan@michonline.com \
    --cc=git@vger.kernel.org \
    --cc=nico-linux-git@schottelius.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).