From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Lennart Borgman Newsgroups: gmane.emacs.devel Subject: Re: Making the tarball with bzr data (was: bzr repository ready?) Date: Mon, 30 Nov 2009 19:15:25 +0100 Message-ID: References: <4B140ACF.9090808@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1259607513 29002 80.91.229.12 (30 Nov 2009 18:58:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 30 Nov 2009 18:58:33 +0000 (UTC) Cc: emacs-devel@gnu.org To: grischka Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 30 19:58:27 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NFBS6-0000UR-Fn for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 19:58:26 +0100 Original-Received: from localhost ([127.0.0.1]:36656 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFBS6-0005Gz-9D for ged-emacs-devel@m.gmane.org; Mon, 30 Nov 2009 13:58:26 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NFAmt-00049T-Li for emacs-devel@gnu.org; Mon, 30 Nov 2009 13:15:51 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NFAmp-00045d-4I for emacs-devel@gnu.org; Mon, 30 Nov 2009 13:15:51 -0500 Original-Received: from [199.232.76.173] (port=42882 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NFAmo-00045T-PI for emacs-devel@gnu.org; Mon, 30 Nov 2009 13:15:46 -0500 Original-Received: from mail-yx0-f191.google.com ([209.85.210.191]:40059) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NFAmo-00022P-OA for emacs-devel@gnu.org; Mon, 30 Nov 2009 13:15:46 -0500 Original-Received: by yxe29 with SMTP id 29so3411997yxe.14 for ; Mon, 30 Nov 2009 10:15:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=KAAYbZ0i8/Al9mjdSMfqUAGNEmnecNKvHppvh1Ilg+o=; b=ix3IaPjBMEa7/lCnveThBBdrYTVsVexf6KoSU35msCvxVe3nEIwnQJ0o0FVXyKBZD2 KjOw9qZCz2U6rbChUAJt4gtmtfdF7ZGBdI1nF18z+K4kAXU1ne336147vwlzIla+XdQR 95Q54n3wGY+Tuw1fcCaUP4qEOq8flTLaLWW6o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=V6CRFK8GY8lZuy3mv9jayaGjJkufsuSifEif5MchKVT/8H2VvNNg8OUd3baoKhiKHN We5lbAhk5L8S9qhJXcHeJPecmhA3Lx0UeqhArAWas5KkMuhEXjfhTN75u7O/e3nRqaey XJDOCqPs8lXh89LEVgU414jZfnDq5sxYUjaZA= Original-Received: by 10.101.210.36 with SMTP id m36mr1806153anq.158.1259604945118; Mon, 30 Nov 2009 10:15:45 -0800 (PST) In-Reply-To: <4B140ACF.9090808@gmx.de> X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:117981 Archived-At: On Mon, Nov 30, 2009 at 7:11 PM, grischka wrote: >> If I already have all the Emacs files locally (possibly with some >> changes) how do I do to make this a bazaar thing? (This must be the >> most common situation, or?) > > In any case you need to get the official emacs bazaar repository > first. Thanks grischka. I believe you, but this seems just crazy to me. What are the reasons for this limitation? Are there any chances this can be fixed? > If you have personal changes, create a branch. > > Then, either: > 1) copy your changed files over the ones in that branch > 2) commit the resulting change as one single patch. > > Or, if you have more than one change and want to have separate > commits for each, use a merge tool such as WinMerge: > 1) compare your directory tree with the new development branch > 2) For each feature: > =C2=A0 - copy the relevant chunks that affect the feature > =C2=A0 - commit with some message > =C2=A0 - repeat 2) until no differences are left. > > Then you could publish your branch for others to test or improve. > > HTH, grischka > >