From: Miklos Vajna <vmiklos@frugalware.org>
To: git@vger.kernel.org
Subject: Deleted file is back - how to investigate?
Date: Sun, 26 Jun 2011 12:32:18 +0200 [thread overview]
Message-ID: <20110626103218.GQ30255@genesis.frugalware.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 648 bytes --]
Hi,
In our public development repo I removed a file in the past, and I guess
with one of the recent merges we got it back. It looks a bit strange:
$ git clone http://frugalware.org/git/pub/frugalware/frugalware-current
$ git checkout 96b33e0
The ogle-gui directory is there:
$ git ls-files|grep ogle-gui
source/xapps-extra/ogle-gui/FrugalBuild
But in case I run git log:
$ git log --full-history --name-status -- source/xapps-extra/ogle-gui
The latest listed commit is the one that deletes it. So how can I see
which commit introduced the file again? (FWIW, we're merging with the
normal recursive strategy, ideally thing special.)
Thanks.
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next reply other threads:[~2011-06-26 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 10:32 Miklos Vajna [this message]
2011-06-26 14:10 ` Deleted file is back - how to investigate? Christof Krüger
2011-06-26 20:25 ` Miklos Vajna
2011-06-26 20:57 ` Andreas Schwab
2011-06-26 21:12 ` Christof Krüger
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=20110626103218.GQ30255@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.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