Re: git commands that only work correctly at top directory
- From
- Matthias Lederhofer <matled@gmx.net>
- Date
- Sep 22, 2006, 11:26 UTC
- Message-ID
- <20060922112615.GB10124@moooo.ath.cx>
- In-Reply-To
- <fcaeb9bf0609220221w3a65af24u9db1da4e1be0d1eb@mail.gmail.com>
Nguyen Thai Ngoc Duy <pclouds@gmail.com> wrote:
Show 7 quoted lines
> Here is the list (checks are done in with 1.4.2.rc4): > count-objects (always 0 objects, 0 kilobytes) > bisect (fatal: Not a git repository: '.git'. Bad HEAD - I need a symbolic > ref) > describe (fatal: Not a valid object name HEAD) > repack (line 42: cd: .git/objects/pack: No such file or directory. And > it creates a new .git directory in current directory)
count-objects and describe work in the current master. repack/bisect/reset and some other commands make only sense from the toplevel directory but anyway I would allow them to be run in a subdirectory and change up to the topdirectory (like git checkout for branch switching). Is there any good reason not to do this? I found it often annoying to go down to the toplevel directory/get a new shell just to reset to HEAD~1.