git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miklos Vajna <vmiklos@frugalware.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jeff King <peff@peff.net>, John Tapsell <johnflux@gmail.com>,
	Git Mailing List <git@vger.kernel.org>
Subject: [PATCH 0/9] fprintf(stderr, "warning: ") -> warning() patches
Date: Tue, 24 Mar 2009 02:09:08 +0100	[thread overview]
Message-ID: <cover.1237856682.git.vmiklos@frugalware.org> (raw)
In-Reply-To: <7v3ad5dxt5.fsf@gitster.siamese.dyndns.org>

On Sun, Mar 22, 2009 at 02:58:46PM -0700, Junio C Hamano <gitster@pobox.com> wrote:
> > Should I rebase the series against current master and resend?
>
> Yes, please, if the overlap with "diff master next" is small enough.

Okay, here it is, applies on top of master. All, except the http-push
one, applies cleanly on top of next as well here.

Miklos Vajna (9):
  http-push: using error() and warning() as appropriate
  builtin-apply: use warning() instead of fprintf(stderr, "warning: ")
  builtin-checkout: use warning() instead of fprintf(stderr, "warning:
    ")
  builtin-fetch-pack: use warning() instead of fprintf(stderr,
    "warning: ")
  builtin-init-db: use warning() instead of fprintf(stderr, "warning:
    ")
  builtin-rm: use warning() instead of fprintf(stderr, "warning: ")
  builtin-show-branch: use warning() instead of fprintf(stderr,
    "warning: ")
  builtin-show-ref: use warning() instead of fprintf(stderr, "warning:
    ")
  refs: use warning() instead of fprintf(stderr, "warning: ")

 builtin-apply.c       |   15 +++++++--------
 builtin-checkout.c    |    4 ++--
 builtin-fetch-pack.c  |    2 +-
 builtin-init-db.c     |    7 +++----
 builtin-rm.c          |    3 +--
 builtin-show-branch.c |    3 +--
 builtin-show-ref.c    |    2 +-
 http-push.c           |    6 +++---
 refs.c                |    8 +++-----
 9 files changed, 22 insertions(+), 28 deletions(-)

  reply	other threads:[~2009-03-24  1:10 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-19  7:36 [PATCH 5/6] Change output "error: " to "Error: " etc John Tapsell
2009-02-19  8:14 ` Thomas Rast
2009-02-19  8:17 ` Jeff King
2009-02-19 12:07   ` [PATCH] http-push: using error() and warning() as appropriate Miklos Vajna
2009-02-19 12:21     ` Jeff King
2009-02-19 12:52       ` [PATCH 0/8] fprintf(stderr, "warning: ") -> warning() patches Miklos Vajna
2009-02-19 12:53         ` [PATCH 1/8] builtin-apply: use warning() instead of fprintf(stderr, "warning: ") Miklos Vajna
2009-02-20  3:02           ` Jeff King
2009-02-20  6:11             ` Junio C Hamano
2009-03-22 11:36               ` Miklos Vajna
2009-03-22 21:58                 ` Junio C Hamano
2009-03-24  1:09                   ` Miklos Vajna [this message]
2009-03-24  1:09                     ` [PATCH 1/9] http-push: using error() and warning() as appropriate Miklos Vajna
2009-03-24  1:09                       ` [PATCH 2/9] builtin-apply: use warning() instead of fprintf(stderr, "warning: ") Miklos Vajna
2009-03-24  1:09                         ` [PATCH 3/9] builtin-checkout: " Miklos Vajna
2009-03-24  1:09                           ` [PATCH 4/9] builtin-fetch-pack: " Miklos Vajna
2009-03-24  1:09                             ` [PATCH 5/9] builtin-init-db: " Miklos Vajna
2009-03-24  1:09                               ` [PATCH 6/9] builtin-rm: " Miklos Vajna
2009-03-24  1:09                                 ` [PATCH 7/9] builtin-show-branch: " Miklos Vajna
2009-03-24  1:09                                   ` [PATCH 8/9] builtin-show-ref: " Miklos Vajna
2009-03-24  1:09                                     ` [PATCH 9/9] refs: " Miklos Vajna
2009-03-24  1:17                                       ` Erik Faye-Lund
2009-03-24  1:23                                         ` Miklos Vajna
2009-03-24  1:28                                           ` Erik Faye-Lund
2009-03-24  1:25                         ` [PATCH 2/9] builtin-apply: " Erik Faye-Lund
2009-03-24  7:35                     ` [PATCH 0/9] fprintf(stderr, "warning: ") -> warning() patches Jeff King
2009-03-24  8:01                       ` Junio C Hamano
2009-02-20  9:41             ` [PATCH 1/8] builtin-apply: use warning() instead of fprintf(stderr, "warning: ") Miklos Vajna
2009-02-19 12:53         ` [PATCH 2/8] builtin-checkout: " Miklos Vajna
2009-02-19 12:53         ` [PATCH 3/8] builtin-fetch-pack: " Miklos Vajna
2009-02-19 12:54         ` [PATCH 4/8] builtin-init-db: " Miklos Vajna
2009-02-19 12:54         ` [PATCH 5/8] builtin-rm: " Miklos Vajna
2009-02-19 12:54         ` [PATCH 6/8] builtin-show-branch: " Miklos Vajna
2009-02-19 12:55         ` [PATCH 7/8] builtin-show-ref: " Miklos Vajna
2009-02-19 12:55         ` [PATCH 8/8] refs: " Miklos Vajna

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=cover.1237856682.git.vmiklos@frugalware.org \
    --to=vmiklos@frugalware.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johnflux@gmail.com \
    --cc=peff@peff.net \
    /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).