From: Pascal Obry <pascal@obry.net>
To: Luciano Rocha <luciano@eurotux.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: something fishy with Git commit and log from file
Date: Wed, 06 Aug 2008 13:01:32 +0200 [thread overview]
Message-ID: <4899848C.6030800@obry.net> (raw)
In-Reply-To: <20080806104432.GG7121@bit.office.eurotux.com>
Luciano,
> If the function doesn't exist, try:
> (gdb) p getwd(malloc(2048))
I got:
(gdb) p (char *)getwd(malloc(2048))
$3 = 0x903680 "/home/obry/dev/repositories/git/AWS"
And this is not the directory I was in. It is the Git root. I was under
/home/obry/dev/repositories/git/AWS/regtests when running the command.
So definitely a Git bug! Can be reproduced with:
$ mkdir repo && cd repo
$ git init
$ mkdir dir
$ cd dir
$ echo file > file
$ echo log > log
$ git add file
$ git commit --file=log
fatal: could not read log file 'log': No such file or directory
Pascal.
--
--|------------------------------------------------------
--| Pascal Obry Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--| http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595
next prev parent reply other threads:[~2008-08-06 11:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 10:30 something fishy with Git commit and log from file Pascal Obry
2008-08-06 10:44 ` Luciano Rocha
2008-08-06 11:01 ` Pascal Obry [this message]
2008-08-06 15:38 ` Junio C Hamano
2008-08-06 16:28 ` Pascal Obry
2008-08-06 16:50 ` Junio C Hamano
2008-08-06 17:08 ` Pascal Obry
2008-08-06 18:43 ` [PATCH] files given on the command line are relative to $cwd Junio C Hamano
2008-08-06 20:14 ` Olivier Marin
2008-08-06 20:19 ` Junio C Hamano
2008-08-06 20:59 ` Junio C Hamano
2008-08-06 20:40 ` Pierre Habouzit
2008-08-07 8:45 ` Samuel Tardieu
2008-08-07 9:03 ` Luciano Rocha
2008-08-07 9:47 ` 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=4899848C.6030800@obry.net \
--to=pascal@obry.net \
--cc=git@vger.kernel.org \
--cc=luciano@eurotux.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).