From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carl Worth Subject: [PATCH] git-push: Update documentation to describe the no-refspec behavior. Date: Tue, 21 Feb 2006 20:28:50 -0800 Message-ID: <87k6borp8d.wl%cworth@cworth.org> Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: multipart/signed; boundary="pgp-sign-Multipart_Tue_Feb_21_20:28:50_2006-1"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Cc: git@vger.kernel.org X-From: git-owner@vger.kernel.org Wed Feb 22 05:30:21 2006 Return-path: Envelope-to: gcvg-git@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FBldq-0002yU-22 for gcvg-git@gmane.org; Wed, 22 Feb 2006 05:30:18 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750810AbWBVEaM (ORCPT ); Tue, 21 Feb 2006 23:30:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751341AbWBVEaL (ORCPT ); Tue, 21 Feb 2006 23:30:11 -0500 Received: from theworths.org ([217.160.253.102]:58006 "EHLO theworths.org") by vger.kernel.org with ESMTP id S1750810AbWBVEaK (ORCPT ); Tue, 21 Feb 2006 23:30:10 -0500 Received: (qmail 382 invoked from network); 21 Feb 2006 23:30:09 -0500 Received: from localhost (HELO raht.cworth.org) (127.0.0.1) by localhost with SMTP; 21 Feb 2006 23:30:09 -0500 To: Junio C Hamano User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.4 Mule/5.0 (SAKAKI) Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: --pgp-sign-Multipart_Tue_Feb_21_20:28:50_2006-1 Content-Type: text/plain; charset=US-ASCII It turns out that the git-push documentation didn't describe what it would do when not given a refspec, (not on the command line, nor in a remotes file). This is fairly important for the user who is trying to understand operations such as: git clone git://something/some/where # hack, hack, hack git push origin I tracked the mystery behavior down to git-send-pack and lifted the relevant portion of its documentation up to git-push, (namely that all refs existing both locally and remotely are updated). Signed-off-by: Carl Worth --- Documentation/git-push.txt | 6 ++++++ 1 files changed, 6 insertions(+), 0 deletions(-) a42f22171f6f3004e524b45b16a9c5cf0386ccf3 diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt index 5b89110..6f4a48a 100644 --- a/Documentation/git-push.txt +++ b/Documentation/git-push.txt @@ -43,6 +43,12 @@ to fast forward the remote ref that matc the optional plus `+` is used, the remote ref is updated even if it does not result in a fast forward update. + +Note: If no explicit refspec is found, (that is neither +on the command line nor in any Push line of the +corresponding remotes file---see below), then all the +refs that exist both on the local side and on the remote +side are updated. ++ Some short-cut notations are also supported. + * `tag ` means the same as `refs/tags/:refs/tags/`. -- 1.2.2.gfdc0 --pgp-sign-Multipart_Tue_Feb_21_20:28:50_2006-1 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQBD++iC6JDdNq8qSWgRAlK3AJ9PGFL7lRz+KBQCyq3mu8Qu4rq5QACggE71 d3nQAiHQbfps9pMW8L7rr+8= =hZxL -----END PGP SIGNATURE----- --pgp-sign-Multipart_Tue_Feb_21_20:28:50_2006-1--