From: Marcel Holtmann <marcel@holtmann.org>
To: "YOSHIFUJI Hideaki / 吉藤英明" <yoshfuji@linux-ipv6.org>
Cc: git@vger.kernel.org
Subject: Re: [COGITO PATCH] fix "cg-Xnormid: command not found" error
Date: Sun, 29 May 2005 11:57:57 +0200 [thread overview]
Message-ID: <1117360678.7072.53.camel@pegasus> (raw)
In-Reply-To: <20050529.121545.77345008.yoshfuji@linux-ipv6.org>
Hi,
> Call cg-Xnormid with ${COGITO_LIB} to fix "cg-Xnormid: command not found"
> error.
I made the same patch, but when I used cg-diff to create the patch, I
got two extra annoying lines at the top.
commit-id: needs update
tree-id: needs update
Index: commit-id
===================================================================
--- c8e987e5e4608c1144293cd3f852210d70b572cb/commit-id (mode:100755)
+++ uncommitted/commit-id (mode:100755)
I think the "needs update" lines came from "git-update-cache --refresh"
and we don't really want them there. Should we simply direct the output
to /dev/null or what?
Regards
Marcel
next prev parent reply other threads:[~2005-05-29 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-29 3:15 [COGITO PATCH] fix "cg-Xnormid: command not found" error YOSHIFUJI Hideaki / 吉藤英明
2005-05-29 9:57 ` Marcel Holtmann [this message]
2005-05-29 12:06 ` Petr Baudis
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=1117360678.7072.53.camel@pegasus \
--to=marcel@holtmann.org \
--cc=git@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 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.