From: Tim Uckun <timuckun@gmail.com>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
Andreas Ericsson <ae@op5.se>, Avery Pennarun <apenwarr@gmail.com>,
git@vger.kernel.org
Subject: Re: can anybody explain the following to a git noob?
Date: Sat, 23 May 2009 20:03:56 +1200 [thread overview]
Message-ID: <855e4dcf0905230103q33508f0eh3aa2838ee71e0a81@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.00.0905221259330.27232@reaper.quantumfyre.co.uk>
> What's in the subdirectory? Is it empty? If so, that would explain what
> you are seeing. Git doesn't track directories - so an empty directory is
> always treated as an untracked file.
The directories are not empty. They contain various tests (unit tests,
integration tests etc).
>
> I don't know if mercurial tracks directories, if it does, then this would
> explain why it behaves diffently to git.
>
That might be the reason.
I am just baffled. I have run that script many times and it always
turns out the same. For example on one run I removed all the .git
directories in all the subdirectories to see if I would get different
results but it didn't help (git mv worked but the messed up
directories remained).
I also tried renaming other directories and similar things happen.
next prev parent reply other threads:[~2009-05-23 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 3:46 can anybody explain the following to a git noob? Tim Uckun
2009-05-22 5:02 ` Avery Pennarun
2009-05-22 5:44 ` Tim Uckun
2009-05-22 9:35 ` Andreas Ericsson
2009-05-22 10:35 ` Tim Uckun
2009-05-22 10:44 ` Johannes Sixt
2009-05-22 11:36 ` Tim Uckun
2009-05-22 12:04 ` Julian Phillips
2009-05-23 8:03 ` Tim Uckun [this message]
2009-05-22 12:22 ` Andreas Ericsson
2009-05-22 17:33 ` Daniel Barkalow
2009-05-23 8:21 ` Tim Uckun
2009-05-25 11:10 ` Heiko Voigt
2009-05-25 12:52 ` Tim Uckun
2009-05-22 11:03 ` Sitaram Chamarty
2009-05-22 13:36 ` Dan Loewenherz
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=855e4dcf0905230103q33508f0eh3aa2838ee71e0a81@mail.gmail.com \
--to=timuckun@gmail.com \
--cc=ae@op5.se \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=julian@quantumfyre.co.uk \
/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).