From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jakub Narebski Subject: Re: [RFC] Terms to add to glossary Date: Tue, 02 May 2006 09:03:42 +0200 Organization: At home Message-ID: References: <7v8xpkq5hw.fsf@assigned-by-dhcp.cox.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-From: git-owner@vger.kernel.org Tue May 02 09:03:11 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 1Faoua-0004Je-Cm for gcvg-git@gmane.org; Tue, 02 May 2006 09:03:08 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932422AbWEBHDE (ORCPT ); Tue, 2 May 2006 03:03:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932425AbWEBHDE (ORCPT ); Tue, 2 May 2006 03:03:04 -0400 Received: from main.gmane.org ([80.91.229.2]:50566 "EHLO ciao.gmane.org") by vger.kernel.org with ESMTP id S932422AbWEBHDB (ORCPT ); Tue, 2 May 2006 03:03:01 -0400 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FaouK-0004Ha-Rt for git@vger.kernel.org; Tue, 02 May 2006 09:02:52 +0200 Received: from 193.0.122.19 ([193.0.122.19]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 May 2006 09:02:52 +0200 Received: from jnareb by 193.0.122.19 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 02 May 2006 09:02:52 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: git@vger.kernel.org X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 193.0.122.19 User-Agent: KNode/0.7.7 Sender: git-owner@vger.kernel.org Precedence: bulk X-Mailing-List: git@vger.kernel.org Archived-At: Junio C Hamano wrote: > cherry-picking:: > In SCM jargon, "cherry pick" means to choose a subset of > changes out of a series of changes (typically commits) > and record them as a separate series of changes on top > of different codebase. In GIT, this is performed by > "git cherry-pick" command to extract the change > introduced by an existing commit and to record it based > on the tip of the current branch as a new commit. That's better. -- Jakub Narebski Warsaw, Poland