git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Fischer <michael@visv.net>
To: git@vger.kernel.org
Subject: 2 questions/nits about commit and config
Date: Sat, 4 Feb 2006 16:23:37 -0500	[thread overview]
Message-ID: <20060204212337.GA8612@blinkenlights.visv.net> (raw)


Hi.

Well, I went ahead and put my current project under git. So far so good.

Two nits: (yeah, I'm a "recovering" CVS user)

1) git commit -m"this is a commit message"  doesn't work. 
   It has to have a space between -m and the first '"'. 
   I *think* this is due to git-commit.sh and how it parses
   the args, but I'm not quite sure of how to try to patch
   that without mucking up the whole works. Very odd
   and hard to figure out what was "wrong" for a CVS user.

2) I can descend into subdirectories in my project, and 
   git diff, git status both work fine, but git commit
   gets annoyed and says "fatal: Not a git repository: '.git'".
   Irksome to say the least, and not a little suprising.
   Is that something which can be fixed, or is there a 
   magic incantation (perhaps in .git/config) to make
   git commit work anywhere in the source tree?

Incidentally, I groped around my git mailbox, and google,
looking for some definitive list/examples of what can
go in the .git/config file. Seems there must be more
than what is listed in the manpage...

Thanks for all the cool work.


Michael
-- 
Michael Fischer                         Happiness is a config option.
michael@visv.net                        Recompile and be happy. 

             reply	other threads:[~2006-02-04 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-04 21:23 Michael Fischer [this message]
2006-02-04 22:13 ` 2 questions/nits about commit and config Junio C Hamano
2006-02-04 22:24   ` Junio C Hamano
2006-02-04 22:59     ` Alan Chandler
2006-02-04 23:00     ` Keith Packard
2006-02-05  5:43       ` Junio C Hamano
2006-02-05  5:58         ` Junio C Hamano
2006-02-05  6:14         ` Daniel Barkalow

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=20060204212337.GA8612@blinkenlights.visv.net \
    --to=michael@visv.net \
    --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).