From: Miklos Vajna <vmiklos@frugalware.org>
To: git@vger.kernel.org
Subject: Strange untracked file behaviour
Date: Wed, 17 Dec 2008 00:24:52 +0100 [thread overview]
Message-ID: <20081216232452.GV5691@genesis.frugalware.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
Hi,
Here is a copy of the udev repo I cloned some time ago:
http://frugalware.org/~vmiklos/files/udev.tar.bz2
I did not modify it, so I thought a simple 'git pull' can update it.
$ git pull
Updating 661a0be..b6626d0
error: Untracked working tree file 'test/sys/class/misc/rtc/dev' would
be removed by merge.
Ok, let's clean the untracked files:
$ git clean -x -d -f
But it does not remove any file.
$ git ls-files|grep test/sys/class/misc/rtc/dev
test/sys/class/misc/rtc/dev
So it seems git-clean is right.
$ git pull -s resolve
Updating 661a0be..b6626d0
error: Untracked working tree file 'test/sys/class/misc/rtc/dev' would
be removed by merge.
So it does not seem to be merge-recursive-related.
Does somebody have an idea what's going on? :)
$ git version
git version 1.6.1.rc1.35.gae26e.dirty
('dirty' is due to non-code changes in my working directory.)
Let me know if you need more details.
Thanks.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-12-16 23:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-16 23:24 Miklos Vajna [this message]
2008-12-17 5:09 ` Strange untracked file behaviour Johannes Schindelin
2008-12-17 14:38 ` Miklos Vajna
2009-01-02 21:59 ` [PATCH 2/3] unpack-trees: fix path search bug in verify_absent Johannes Schindelin
2009-01-03 14:01 ` Miklos Vajna
-- strict thread matches above, loose matches on Subject: below --
2009-01-01 20:54 unpack-trees: fix D/F conflict bugs " Clemens Buchacher
2009-01-01 20:54 ` [PATCH 1/3] unpack-trees: handle failure " Clemens Buchacher
2009-01-01 20:54 ` [PATCH 2/3] unpack-trees: fix path search bug " Clemens Buchacher
2009-01-01 20:54 ` [PATCH 3/3] unpack-trees: remove redundant path search " Clemens Buchacher
2009-01-06 8:19 ` Junio C Hamano
2009-01-02 21:59 ` [PATCH 2/3] unpack-trees: fix path search bug " Johannes Schindelin
2009-01-03 10:39 ` Clemens Buchacher
2009-01-03 12:53 ` Johannes Schindelin
2009-01-04 10:01 ` Junio C Hamano
2009-01-04 20:01 ` Clemens Buchacher
2009-01-06 19:35 ` Johannes Schindelin
2011-01-13 2:24 ` [RFC/PATCH 0/2] unpack-trees: handle lstat failures " Jonathan Nieder
2011-01-13 2:26 ` [PATCH 1/2] unpack-trees: handle lstat failure for existing directory Jonathan Nieder
2011-01-13 4:37 ` Miles Bader
2011-01-13 5:38 ` Jonathan Nieder
2011-01-13 2:28 ` [PATCH 2/2] unpack-trees: handle lstat failure for existing file Jonathan Nieder
2011-01-13 20:20 ` [RFC/PATCH 0/2] unpack-trees: handle lstat failures in verify_absent Clemens Buchacher
2009-01-01 21:28 ` unpack-trees: fix D/F conflict bugs " Junio C Hamano
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=20081216232452.GV5691@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;
as well as URLs for NNTP newsgroup(s).