All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed L Cashin <ecashin@coraid.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: git add / update-cache --add fails.
Date: Wed, 27 Apr 2005 13:38:31 -0400	[thread overview]
Message-ID: <87r7gwf7c8.fsf@coraid.com> (raw)
In-Reply-To: <20050427173059.GE22956@pasky.ji.cz> (Petr Baudis's message of "Wed, 27 Apr 2005 19:30:59 +0200")

Petr Baudis <pasky@ucw.cz> writes:

...
>> +		fprintf(stderr, "update-cache Error: %s\n", strerror(errno));
...
> FWIW, I have this in my tree for some time already. :-)

OK, nice.

...
>
>> By the way, I created that patch with "git diff" in my git-pasky
>> working directory.  Strangely, I had to redirect standard error to the
>> same place as standard output in order to get the filename in the diff
>> output.  I didn't check why the filename is on standard error,
>> though.
>
> Interesting. Anyway, you are apparently using some quite antique
> git-pasky version.

It wasn't on purpose!  :)

Thinking back, my "git pull" probably didn't merge correctly because
it was too old.  I'll just blow away the old one and start over.

-- 
  Ed L Cashin <ecashin@coraid.com>


  reply	other threads:[~2005-04-27 17:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-25 21:26 git add / update-cache --add fails Rhys Hardwick
2005-04-25 21:50 ` Rhys Hardwick
2005-04-25 21:52 ` Rhys Hardwick
2005-04-25 22:09   ` Chris Wedgwood
2005-04-26  0:47   ` Linus Torvalds
2005-04-26  6:26     ` Rhys Hardwick
2005-04-27  2:35       ` Herbert Xu
2005-04-27 16:48         ` Ed L Cashin
2005-04-27 17:30           ` Petr Baudis
2005-04-27 17:38             ` Ed L Cashin [this message]
2005-04-28  1:01             ` Paul Jackson
2005-04-28  1:05               ` Petr Baudis
2005-04-28  1:20                 ` Paul Jackson
2005-04-26  1:38   ` 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=87r7gwf7c8.fsf@coraid.com \
    --to=ecashin@coraid.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@ucw.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.