From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: minor bzr->git changes missed Date: Fri, 14 Nov 2014 07:42:56 +0200 Message-ID: <838ujejq1r.fsf@gnu.org> References: <20141113110017.3f8bc06c@jabberwock.cb.piermont.com> <83a93vkr4u.fsf@gnu.org> <20141113113738.74f15110@jabberwock.cb.piermont.com> <8361ejkolo.fsf@gnu.org> <5464E7E0.9030502@cs.ucla.edu> <83y4rfj94o.fsf@gnu.org> <20141113124405.7621c9af@jabberwock.cb.piermont.com> <83sihnj7nj.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1415943807 26075 80.91.229.3 (14 Nov 2014 05:43:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 14 Nov 2014 05:43:27 +0000 (UTC) Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org, perry@piermont.com To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 14 06:43:19 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xp9fD-0008Og-16 for ged-emacs-devel@m.gmane.org; Fri, 14 Nov 2014 06:43:19 +0100 Original-Received: from localhost ([::1]:34982 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xp9fC-00009C-K2 for ged-emacs-devel@m.gmane.org; Fri, 14 Nov 2014 00:43:18 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52784) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xp9ew-00008z-Nl for emacs-devel@gnu.org; Fri, 14 Nov 2014 00:43:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xp9er-0001Rn-Oy for emacs-devel@gnu.org; Fri, 14 Nov 2014 00:43:02 -0500 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:56432) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xp9er-0001Rj-HM for emacs-devel@gnu.org; Fri, 14 Nov 2014 00:42:57 -0500 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0NF000500KQJ7M00@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Fri, 14 Nov 2014 07:42:56 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NF000432L7JZA80@a-mtaout20.012.net.il>; Fri, 14 Nov 2014 07:42:56 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177036 Archived-At: > From: Lars Magne Ingebrigtsen > Cc: "Perry E. Metzger" , eggert@cs.ucla.edu, emacs-devel@gnu.org > Date: Thu, 13 Nov 2014 22:54:35 +0100 > MailScanner-NULL-Check: 1416520475.64046@ljevEl7WkIEO5ZseDB61fA > > Eli Zaretskii writes: > > >> For reference, is there a description of the full development > >> process, updated for the git world, one can read? > > > > Yes, admin/notes/repo and admin/notes/commits. > > I scanned this and I scanned Git for Emacs Devs, but I'm still not sure > how to push stuff to the emacs-24 branch. > > Could someone please just write recipe on how to do this, starting with > > git clone --local emacs emacs-24 AFAIU, by using "clone --local", you defined a personalized workflow that is not what the Wiki describes. The Wiki describes the situation where you have a repository cloned from the remote. Then you just "git checkout" the branch, make your changes, commit them, and push them. Exactly like you do with master, with the addition of the checkout step. It's unreasonable to expect the related documentation to describe every possible personal workflow out there. If you use your own workflow, you are expected to know how, or google, or ask specific questions.