From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] usage.c: remove unused functions
Date: Thu, 25 Sep 2008 14:53:01 +0200 [thread overview]
Message-ID: <gbg1jc$hjm$1@ger.gmane.org> (raw)
In-Reply-To: 200809251348.42789.trast@student.ethz.ch
Thomas Rast wrote:
> Nanako Shiraishi wrote:
>> This removes three functions that are not used anywhere.
> [...]
>> -void set_usage_routine(void (*routine)(const char *err) NORETURN)
> [...]
>> -void set_error_routine(void (*routine)(const char *err, va_list params))
> [...]
>> -void set_warn_routine(void (*routine)(const char *warn, va_list params))
>
> These blame to the following commit:
>
> commit 39a3f5ea7c0352a530338d30d4e618f6b4db84e4
> Author: Petr Baudis <pasky@suse.cz>
> Date: Sat Jun 24 04:34:38 2006 +0200
>
> Customizable error handlers
>
> This patch makes the usage(), die() and error() handlers customizable.
> Nothing in the git code itself uses that but many other libgit users
> (like Git.pm) will.
> [...]
>
> So apparently the intent was that they would only be used from outside
> Git. I don't know whether anyone still plans to do that, but they're
> certainly not "just" unused.
By the way, those functions could be used to implement
"git --silent <cmd>", which is equivalent of "git <cmd> 2>/dev/null"
(which you don't always can do easily).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
prev parent reply other threads:[~2008-09-25 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 9:41 [PATCH] usage.c: remove unused functions Nanako Shiraishi
2008-09-25 11:48 ` Thomas Rast
2008-09-25 12:48 ` Petr Baudis
2008-09-25 14:51 ` Shawn O. Pearce
2008-09-25 20:43 ` Jonas Fonseca
2008-09-29 6:35 ` Lars Hjemli
2008-09-25 12:53 ` Jakub Narebski [this message]
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='gbg1jc$hjm$1@ger.gmane.org' \
--to=jnareb@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).