From: Pierre Habouzit <madcoder@debian.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] git-send-pack: don't consider branch lagging behind as errors.
Date: Thu, 19 Jun 2008 18:28:01 +0200 [thread overview]
Message-ID: <20080619162801.GA2468@artemis.madism.org> (raw)
In-Reply-To: <20080619151110.GA31654@sigill.intra.peff.net>
[-- Attachment #1: Type: text/plain, Size: 1906 bytes --]
On Thu, Jun 19, 2008 at 03:11:10PM +0000, Jeff King wrote:
> On Thu, Jun 19, 2008 at 03:52:00PM +0200, Pierre Habouzit wrote:
> > > - there is a possible danger with "git push -f", in that you force
> > > both rejected branches as well as stale branches. Junio and I
> > Well afaict this is a separate issue, as we're (with such a patch)
> > only changing what gets printed on the console, not the internal
> > behavior. So solving this second issue should not really be a
> > precondition to the inclusion of such a patch.
>
> It is a separate issue, but it is exacerbated by hiding stale refs.
> Imagine:
>
> $ git push
> To /path/to/repo
> ! [rejected] master -> master (non-fast forward)
>
> $ git push -f
> To /path/to/repo
> + 0abfa88...c1ed93b master -> master (forced update)
> + 0329485...3498576 stale_branch -> stale_branch (forced update)
>
> I think that is a nasty surprise to spring on an unsuspecting user.
> Another solution might be "-f" not pushing rewound branches, but then we
> need a way to specify "no, really, push this rewound branch". Perhaps
> "-f -f"?
Well then we could keep the [stalled] lines for now until this issue
is resolved then, despite what the people at the beginning of the other
thread complained about. My real issue is that I have my shell
configured so that my prompt becomes inverted if the last command
failed. So do many people I know, and well, git push for stalled
references should just not generate an error. _this_ is my sole concern
:)
> > Please please please do :)
> > The exit 1 of git-push is really annoying me these days.
>
> OK, I will try to take a look in the next few days.
>
> -Peff
--
·O· Pierre Habouzit
··O madcoder@debian.org
OOO http://www.madism.org
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-06-19 16:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 10:51 [PATCH] git-send-pack: don't consider branch lagging behind as errors Pierre Habouzit
2008-06-19 13:37 ` Jeff King
2008-06-19 13:52 ` Pierre Habouzit
2008-06-19 15:11 ` Jeff King
2008-06-19 16:28 ` Pierre Habouzit [this message]
2008-06-19 18:33 ` Junio C Hamano
2008-06-20 9:55 ` Pierre Habouzit
2008-06-20 22:14 ` しらいしななこ
2008-06-26 7:50 ` Jeff King
2008-06-26 8:19 ` Junio C Hamano
2008-06-26 13:28 ` Pierre Habouzit
2008-06-28 4:33 ` Jeff King
2008-06-28 4:34 ` 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=20080619162801.GA2468@artemis.madism.org \
--to=madcoder@debian.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).