git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <junkio@cox.net>
Cc: Bill Lear <rael@zopyra.com>,
	git@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: How can git pull be up-to-date and git push fail?
Date: Sat, 7 Apr 2007 17:32:33 -0400	[thread overview]
Message-ID: <20070407213233.GA23234@coredump.intra.peff.net> (raw)
In-Reply-To: <7vy7l3c1uz.fsf@assigned-by-dhcp.cox.net>

On Sat, Apr 07, 2007 at 02:26:44PM -0700, Junio C Hamano wrote:

> Yes, that is exactly why I suggested "git push" without explicit
> refspecs to drive the plumbings to push only matching branches.
> So if you are worried about breaking backward compatibility for
> real men (iow people who use git-send-pack directly), it would
> be a less impact change to (1) add --matching-heads option to
> send-pack and perhaps http-push, and change their behaviour only
> in that case, and (2) pass that option when git-push did not get
> explicit refspecs to send from the user, either from the command
> line nor from the config.

Ah, I (obviously) didn't pick that up from your original message. Let me
rework my patch and see if I can get something more reasonable.

-Peff

      reply	other threads:[~2007-04-07 21:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-05 12:15 How can git pull be up-to-date and git push fail? Bill Lear
2007-04-05 13:49 ` Jeff King
2007-04-05 14:07   ` Bill Lear
2007-04-05 14:25     ` Bill Lear
2007-04-05 20:46     ` Jeff King
2007-04-05 20:55       ` Bill Lear
2007-04-07 16:16         ` Jeff King
2007-04-05 21:18       ` Junio C Hamano
2007-04-06  2:52         ` Jeff King
2007-04-06 21:44           ` Junio C Hamano
2007-04-07 17:07             ` Jeff King
2007-04-07 21:26               ` Junio C Hamano
2007-04-07 21:32                 ` Jeff King [this message]

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=20070407213233.GA23234@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=rael@zopyra.com \
    --cc=torvalds@linux-foundation.org \
    /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).