From: Matthias Kestenholz <lists@spinlock.ch>
To: Andreas Ericsson <ae@op5.se>
Cc: Alex Riesen <raa.lkml@gmail.com>,
Simon 'corecode' Schubert <corecode@fs.ei.tum.de>,
Junio C Hamano <junkio@cox.net>,
Yasushi SHOJI <yashi@atmark-techno.com>,
git@vger.kernel.org
Subject: Re: git ls-files -o under .git/ prints all repository files
Date: Fri, 19 Jan 2007 14:46:54 +0100 [thread overview]
Message-ID: <1169214414.18684.25.camel@localhost.localdomain> (raw)
In-Reply-To: <45B0C7E6.4020509@op5.se>
On Fri, 2007-01-19 at 14:30 +0100, Andreas Ericsson wrote:
> Alex Riesen wrote:
> > On 1/19/07, Simon 'corecode' Schubert <corecode@fs.ei.tum.de> wrote:
> >> >
> >>
> >> % cd .hg && hg status -A .
> >> abort: path contains illegal component: .hg
> >>
> >> I think this is a sensible thing to do.
> >
> > No, it isn't. It is not unlikely to have repo in repo
> > (and some people already have them).
> > Mercurial is wrong here.
>
> For managing repos inside repos (onion repos?) I think it should
> be safe to abort if we're not at top-level.
>
Why not check for /.git/ somewhere inside the current working directory
(pwd) ? That's the way mercurial does it currently, and I think that is
a sane thing to do _if_ you want to protect the user from his own
stupidity.
next prev parent reply other threads:[~2007-01-19 13:47 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
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 [this message]
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=1169214414.18684.25.camel@localhost.localdomain \
--to=lists@spinlock.ch \
--cc=ae@op5.se \
--cc=corecode@fs.ei.tum.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=raa.lkml@gmail.com \
--cc=yashi@atmark-techno.com \
/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