From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Michael Schubert <mschub@elegosoft.com>,
Git List <git@vger.kernel.org>
Subject: Re: Proposal: branch.<name>.remotepush
Date: Fri, 08 Feb 2013 00:16:53 -0800 [thread overview]
Message-ID: <7v622343uy.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20130208074813.GA7337@elie.Belkin> (Jonathan Nieder's message of "Thu, 7 Feb 2013 23:48:13 -0800")
Jonathan Nieder <jrnieder@gmail.com> writes:
> "Wait, why did the remote rewind?"
Oh, I am very well aware of that glitch.
"git push" has this hack to pretend as if the pusher immediately
turned around and fetched from the remote.
It shouldn't have been made to do so unconditionally; instead it
should have been designed to give the pushee a way to optionally
tell you "I acccept this push, but you may not see it to be updated
to that exact value you pushed when you fetched from me right now".
The hack is not my design; it was not even something I accepted
without complaints, so I can badmouth about it all I want without
hesitation ;-)
More importantly, we could fix it if we wanted to.
next prev parent reply other threads:[~2013-02-08 8:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 16:14 Proposal: branch.<name>.remotepush Ramkumar Ramachandra
2013-02-07 17:45 ` Michael Schubert
2013-02-07 19:37 ` Ramkumar Ramachandra
2013-02-07 19:49 ` Ramkumar Ramachandra
2013-02-07 20:14 ` Ramkumar Ramachandra
2013-02-07 23:30 ` Jonathan Nieder
2013-02-07 23:41 ` Junio C Hamano
2013-02-08 7:48 ` Jonathan Nieder
2013-02-08 8:16 ` Junio C Hamano [this message]
2013-02-08 10:38 ` Michael J Gruber
2013-02-08 17:11 ` Junio C Hamano
2013-02-08 17:16 ` Junio C Hamano
2013-02-08 18:29 ` Ramkumar Ramachandra
2013-02-08 19:13 ` Junio C Hamano
2013-02-08 18:36 ` Jonathan Nieder
2013-02-08 18:42 ` Ramkumar Ramachandra
2013-02-08 19:18 ` Junio C Hamano
2013-02-09 7:29 ` Ramkumar Ramachandra
2013-02-08 4:48 ` Jeff King
2013-02-08 6:08 ` Junio C Hamano
2013-02-08 6:28 ` Jeff King
2013-02-08 6:45 ` Junio C Hamano
2013-02-08 9:22 ` Jeff King
2013-02-08 17:06 ` Junio C Hamano
2013-02-08 18:03 ` Ramkumar Ramachandra
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=7v622343uy.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=mschub@elegosoft.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).