From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Jason Garber <jgarber@ionzoft.com>,
Jay Soffian <jaysoffian@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH 1/3] push: indicate partialness of error message
Date: Tue, 19 Feb 2008 13:34:40 -0800 [thread overview]
Message-ID: <7vablwiqa7.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 20080219162501.GA30451@sigill.intra.peff.net
Jeff King <peff@peff.net> writes:
> This patch series is meant to address some user issues encountered in
> the recent thread "git push [rejected] question". It's entirely
> message and documentation updates.
Thanks; I think all of them are fine 'maint' material.
Distinguishing between [rejected] and [stale] would belong in
1.5.5 if it is really needed. Together with the "git checkout
notices forks" enhancement on Daniel's git-checkout rewritten in
C, I think it would solve the issue in the "push [rejected]
question".
next prev parent reply other threads:[~2008-02-19 21:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 16:25 [PATCH 1/3] push: indicate partialness of error message Jeff King
2008-02-19 21:34 ` Junio C Hamano [this message]
2008-02-19 21:54 ` Jeff King
2008-02-20 0:09 ` 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=7vablwiqa7.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
--cc=jgarber@ionzoft.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).