From: Yasushi SHOJI <yashi@atmark-techno.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git ls-files -o under .git/ prints all repository files
Date: Fri, 19 Jan 2007 16:41:56 +0900 [thread overview]
Message-ID: <87k5zjsbsr.wl@mail2.atmark-techno.com> (raw)
In-Reply-To: <7vwt3jjywc.fsf@assigned-by-dhcp.cox.net>
At Thu, 18 Jan 2007 22:47:47 -0800,
Junio C Hamano wrote:
>
> Yasushi SHOJI <yashi@atmark-techno.com> writes:
>
> > ls-files -o prints all files under .git if you are in the .git
> > directory. this is pretty dangerous since we now have git clean to
> > delete files marked others.
> >
> > sure in UNIX env., you can easily shoot yourself in the foot. but it'd
> > might be nice to help newbies.
>
> It's amusing to see that people can find obscure ways to shoot
> themselves in the foot.
>
> Amusing problems deserve an equally amusing solution.
Unfortunately, the amusing ;-) solution doesn't prevent them all.
$ cd .git/objects
$ git ls-fiels -o
0f/902e4635d4d7b8e532b485eeeb6399d0910710
bc/2d2dcb34e8313627d45ad6ef38beddf560501d
ce/013625030ba8dba906f756967f9e9ca394464a
$ git clean -d -x
Removing 0f/
Removing bc/
Removing ce/
Removing info/
Removing pack/
I presume that if the cwd is the direct decedent of the current
GIT_DIR, ls-files should print error saying "you are not in the
working dir".
or, just ignore '.git/*' all the time.
$ git ls-files -o
HEAD
config
:
$ git ls-files -o --exclude='.git/*'
$
What do you think?
--
yashi
next prev parent reply other threads:[~2007-01-19 7:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 1:04 git ls-files -o under .git/ prints all repository files Yasushi SHOJI
2007-01-19 6:47 ` Junio C Hamano
2007-01-19 7:27 ` Andy Parkins
2007-01-19 8:32 ` Junio C Hamano
2007-01-19 9:04 ` Andy Parkins
2007-01-19 7:41 ` Yasushi SHOJI [this message]
2007-01-19 7:51 ` Simon 'corecode' Schubert
2007-01-19 7:57 ` Alex Riesen
2007-01-19 8:07 ` Simon 'corecode' Schubert
2007-01-19 8:32 ` Alex Riesen
2007-01-19 9:04 ` Simon 'corecode' Schubert
2007-01-19 9:33 ` Alex Riesen
2007-01-19 10:10 ` Simon 'corecode' Schubert
2007-01-19 10:38 ` Alex Riesen
2007-01-19 12:19 ` Simon 'corecode' Schubert
2007-01-19 13:30 ` Andreas Ericsson
2007-01-19 13:46 ` Matthias Kestenholz
2007-01-19 15:00 ` Johannes Schindelin
2007-01-19 19:03 ` Junio C Hamano
2007-01-23 11:12 ` Yasushi SHOJI
2007-01-23 12:30 ` [PATCH] Commands requiring a work tree must not run in GIT_DIR Johannes Schindelin
2007-01-24 11:44 ` Junio C Hamano
2007-01-24 14:14 ` Johannes Schindelin
2007-01-24 22:51 ` Junio C Hamano
2007-01-19 8:02 ` git ls-files -o under .git/ prints all repository files Alex Riesen
2007-01-19 8:01 ` Alex Riesen
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=87k5zjsbsr.wl@mail2.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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