From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Git transition checklist Date: Sat, 11 Jan 2014 21:32:31 +0100 Organization: Organization?!? Message-ID: <87eh4efee8.fsf@fencepost.gnu.org> References: <20140108135200.8ECF9380834@snark.thyrsus.com> <1738kywelh.fsf@fencepost.gnu.org> <20140108200216.GB5374@thyrsus.com> <6pr48h52eq.fsf@fencepost.gnu.org> <87y52pg4ov.fsf@uwakimon.sk.tsukuba.ac.jp> <838uupeitt.fsf@gnu.org> <87sisxfu6q.fsf@uwakimon.sk.tsukuba.ac.jp> <87txddmmcj.fsf@igel.home> <87lhypfcs4.fsf@uwakimon.sk.tsukuba.ac.jp> <831u0hdrcp.fsf@gnu.org> <83zjn2ani2.fsf@gnu.org> <3efvoujn6q.fsf@fencepost.gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1389472373 17110 80.91.229.3 (11 Jan 2014 20:32:53 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 11 Jan 2014 20:32:53 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jan 11 21:33:00 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 1W25Eq-000826-7O for ged-emacs-devel@m.gmane.org; Sat, 11 Jan 2014 21:33:00 +0100 Original-Received: from localhost ([::1]:35383 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W25El-00052z-NF for ged-emacs-devel@m.gmane.org; Sat, 11 Jan 2014 15:32:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45464) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W25Ed-00052o-1h for emacs-devel@gnu.org; Sat, 11 Jan 2014 15:32:52 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1W25EX-0000Z4-SA for emacs-devel@gnu.org; Sat, 11 Jan 2014 15:32:46 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:57694) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1W25EX-0000Xq-LX for emacs-devel@gnu.org; Sat, 11 Jan 2014 15:32:41 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1W25EW-0007ma-Eg for emacs-devel@gnu.org; Sat, 11 Jan 2014 21:32:40 +0100 Original-Received: from x2f3cf5e.dyn.telefonica.de ([2.243.207.94]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 11 Jan 2014 21:32:40 +0100 Original-Received: from dak by x2f3cf5e.dyn.telefonica.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 11 Jan 2014 21:32:40 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 23 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: x2f3cf5e.dyn.telefonica.de X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) Cancel-Lock: sha1:Etl4h2F3rNoqWipnGkKE2ocum1c= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 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:168119 Archived-At: Glenn Morris writes: > Oh look, what great timing: > > https://lists.ubuntu.com/archives/bazaar/2014q1/075790.html > > I've forked Bazaar, as bzr3, in order to move the codebase to Python 3.x > and remove things no longer required to make that effort easier. > > Not dead, only sleeping? How is it not dead if a _fork_ appears appropriate for supporting the current Python version? While I don't know the circumstances involved, for a live project porting to the current version of its language would happen in a _branch_ of the upstream repository. A _fork_ will take a lot of effort before it can gather the kind of support an original project once had. -- David Kastrup