From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Sat, 01 Oct 2005 10:24:54 GMT
Subject: Re: Destructive side-effect of "cg-status"
Message-ID: <46a038f90510010324h65bea422tf9a519a014ed4844@mail.gmail.com>
In-Reply-To: <20050930160353.F025C352B7B@atlas.denx.de>

On 10/1/05, Wolfgang Denk <wd@denx.de> wrote:
> So far I  thought  "cg-status"  is  a  harmless  command  which  just
> displays  some  status information. It ain't so. One of our engineers
> reported a  corrupted  repository  after  I  ran  "cg-status"  in  his
> directory:

Interesting... cg-status, and sometimes cg-diff, have to update the
index. The index is the trick behind git's performance (and some other
smarts). It's never really touched by Cogito, but by the git-*-index
commands.

Perhaps git-*-index commands should check ownership vs current uid and
print a warning?

cheers,


martin