From: "Thomas Kolejka" <Thomas.Kolejka@gmx.at>
To: git@vger.kernel.org
Cc: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
Subject: Re: git commands that only work correctly at top directory
Date: Fri, 22 Sep 2006 19:08:59 +0200 [thread overview]
Message-ID: <20060922170859.119780@gmx.net> (raw)
In-Reply-To: <fcaeb9bf0609220221w3a65af24u9db1da4e1be0d1eb@mail.gmail.com>
-------- Original-Nachricht --------
Datum: Fri, 22 Sep 2006 16:21:09 +0700
Von: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
An: git@vger.kernel.org
Betreff: git commands that only work correctly at top directory
Did you set $GIT_DIR? ... to an absolute path or "./.git" ?
> Here is the list (checks are done in with 1.4.2.rc4):
> count-objects (always 0 objects, 0 kilobytes)
Works for me in every directory with GIT_DIR abolute or ./.git
> bisect (fatal: Not a git repository: '.git'. Bad HEAD - I need a symbolic
> ref)
with an absolute GIT_DIR works from every directory - at least bisect start
> describe (fatal: Not a valid object name HEAD)
with an absolute GIT_DIR works from every directory.
v1.4.1-gcddb939
> repack (line 42: cd: .git/objects/pack: No such file or directory. And
> it creates a new .git directory in current directory)
> git format-patch in subdir generates files in topdir instead of
> current dir as documented in its man page
>
> BTW, either git blame or git annotate should be available in git help's
> listing.
> git format-patch with no argument shows nothing. It should show help
> usage instead.
> I might miss some commands because I only tested commands I'm familiar
> with.
> --
> Duy
Thomas
--
NEU: GMX DSL Sofort-Start-Set - blitzschnell ins Internet!
Echte DSL-Flatrate ab 0,- Euro* http://www.gmx.net/de/go/dsl
next prev parent reply other threads:[~2006-09-22 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 9:21 git commands that only work correctly at top directory Nguyen Thai Ngoc Duy
2006-09-22 11:12 ` [PATCH] format-patch: use cwd as default output directory Matthias Lederhofer
2006-09-28 10:25 ` Nguyen Thai Ngoc Duy
2006-09-28 16:16 ` Junio C Hamano
2006-09-28 19:55 ` [PATCH] git-format-patch: fix bug using -o in subdirectories Matthias Lederhofer
2006-09-22 11:26 ` git commands that only work correctly at top directory Matthias Lederhofer
2006-09-22 12:57 ` Nguyen Thai Ngoc Duy
2006-09-23 15:16 ` Petr Baudis
2006-09-22 15:10 ` [PATCH] git-repack: allow git-repack to run in subdirectory Jeff King
2006-09-22 17:08 ` Thomas Kolejka [this message]
2006-09-25 2:31 ` [PATCH/RESEND] " Jeff King
2006-09-25 3:16 ` Junio C Hamano
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=20060922170859.119780@gmx.net \
--to=thomas.kolejka@gmx.at \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.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;
as well as URLs for NNTP newsgroup(s).