From: "Nguyen Thai Ngoc Duy" <pclouds@gmail.com>
To: git@vger.kernel.org
Subject: git commands that only work correctly at top directory
Date: Fri, 22 Sep 2006 16:21:09 +0700 [thread overview]
Message-ID: <fcaeb9bf0609220221w3a65af24u9db1da4e1be0d1eb@mail.gmail.com> (raw)
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)
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
next reply other threads:[~2006-09-22 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 9:21 Nguyen Thai Ngoc Duy [this message]
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 ` git commands that only work correctly at top directory Thomas Kolejka
2006-09-25 2:31 ` [PATCH/RESEND] git-repack: allow git-repack to run in subdirectory 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=fcaeb9bf0609220221w3a65af24u9db1da4e1be0d1eb@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
/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).