Re: git commands that only work correctly at top directory
- From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
- Date
- Sep 22, 2006, 12:57 UTC
- Message-ID
- <fcaeb9bf0609220557m7802a446nd47a9560c6977b31@mail.gmail.com>
- In-Reply-To
- <20060922112615.GB10124@moooo.ath.cx>
On 9/22/06, Matthias Lederhofer <matled@gmx.net> wrote:
> count-objects and describe work in the current master.
Yes. Somehow my master is not updated to origin :(
Show 6 quoted lines
> 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.
In case there is good reason not to do it, I'd like those commands to tell users run them in top directory. (Although I prefer to run it everywhere, I hate to cd around just for one command)
-- Duy