git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry D'Anna <larry@elder-gods.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2010, #05; Sun, 21)
Date: Sun, 21 Feb 2010 22:08:29 -0500	[thread overview]
Message-ID: <20100222030829.GA32020@cthulhu> (raw)
In-Reply-To: <7vtytacebd.fsf@alter.siamese.dyndns.org>

* Junio C Hamano (gitster@pobox.com) [100221 19:19]:

> [Stalled]
> 
> * ld/push-porcelain (2010-02-09) 4 commits
>  - git-push: fix an error message so it goes to stderr
>  - git-push: make git push --dry-run --porcelain exit with status 0 even if updates will be rejected
>  - git-push: send "To <remoteurl>" messages to the standard output in --porcelain mode
>  - git-push: squelch advice message if in --porcelain mode
> 
> This needs further simplification, judging from the previous discussion?

I was waiting for Michael Lukashov to put out the next version of his
refactoring series to do another of this (there was some concern there would be
a merge issue between this and that).  Aside from the --quiet issue, are there
any other changes this series needs?

      --larry

  reply	other threads:[~2010-02-22  3:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22  0:19 What's cooking in git.git (Feb 2010, #05; Sun, 21) Junio C Hamano
2010-02-22  3:08 ` Larry D'Anna [this message]
2010-02-22  7:35 ` Johannes Sixt
2010-02-22  7:49   ` Junio C Hamano
2010-02-22  8:17     ` Björn Gustavsson
2010-02-22  8:37       ` Johannes Schindelin
2010-02-22  9:48         ` Thomas Rast
2010-02-22 10:01           ` Thomas Rast
2010-02-22 10:08           ` Johannes Schindelin
2010-02-22 10:37             ` Jeff King
2010-02-22 10:52 ` Jeff King
2010-02-22 20:21   ` Junio C Hamano
2010-02-23  0:53     ` Jeff King

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=20100222030829.GA32020@cthulhu \
    --to=larry@elder-gods.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).