From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Catalin Marinas" Subject: Re: [ANNOUNCE] Stacked GIT 0.14.2 Date: Mon, 24 Mar 2008 23:40:04 +0000 Message-ID: References: <47E81037.5030808@keyaccess.nl> <7vlk47ua3v.fsf@gitster.siamese.dyndns.org> <47E82BDD.9060507@keyaccess.nl> <47E837E8.7000606@keyaccess.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "Junio C Hamano" , "Jan Engelhardt" , git , "Linux Kernel Mailing List" , "Josef Sipek" , "Linus Torvalds" To: "Rene Herman" X-From: git-owner@vger.kernel.org Tue Mar 25 00:40:54 2008 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1JdwHd-0000y7-Qg for gcvg-git-2@gmane.org; Tue, 25 Mar 2008 00:40:54 +0100 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755804AbYCXXkI (ORCPT ); Mon, 24 Mar 2008 19:40:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755776AbYCXXkH (ORCPT ); Mon, 24 Mar 2008 19:40:07 -0400 Received: from wx-out-0506.google.com ([66.249.82.235]:61597 "EHLO wx-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755805AbYCXXkF (ORCPT ); Mon, 24 Mar 2008 19:40:05 -0400 Received: by wx-out-0506.google.com with SMTP id h31so3235632wxd.4 for ; Mon, 24 Mar 2008 16:40:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=583aWPyzbYpsrW2Pu5X74STA8acB1I+POkpCVopNbXc=; b=YT26IexU3KazGFVnqmV6SWQB7svhfMMzQn5q+ZpC82G6nt5tRCkrInFh/TeZGIB5+BPiVcPFwKvLQFg71bgjlSeZCq9yxAhxwWWrI0IJnJUIPmVNdj+4XFkLS+jwVHUDVauC1rkF23qwZ6nyBx+AM62R7UjyyAjA8k5RDeH6N1Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=DF18G7oBreAe6d8vdW5rZlvLyW4Svpo+Deepn8KjaFZubsPJbZMFJpBT+HWA1a/GnMwAaweBdKTETtuxSKzlgsrs3UrwcecdK6yJI71bhTCKPiXHMwkLtApygnyJIQpfEMWc/BM9rRoy0eKJVDaLkJTDzWrfNqj9Ed0Whbn3Muc= Received: by 10.141.145.11 with SMTP id x11mr2712349rvn.215.1206402004466; Mon, 24 Mar 2008 16:40:04 -0700 (PDT) Received: by 10.141.175.11 with HTTP; Mon, 24 Mar 2008 16:40:04 -0700 (PDT) In-Reply-To: <47E837E8.7000606@keyaccess.nl> Content-Disposition: inline Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: On 24/03/2008, Rene Herman wrote: > used to use quilt and although I > didn't much care for its linear nature when managing an entire tree, it > probably works out well for private topic branches. Not overly sure of added > practical value over git rebase, but I did like the simple nature of > shuffling things around by just editing a series file back when I was using > quilt. Keeps one on top of things, so to speak (<-- amusing play on words). Git rebasing is useful but using a patch management tool is much easier, especially when you need to post a series of patches multiple times while implementing others' comments. And this is not only for private branches but public ones that are meant for upstream merging. The problem with these tools is that they rewrite the history of the repository but they are OK if you aren't in a position where people need to base their work on your tree. I would much prefer to simply commit the additional comments at the top of a branch without changing the history but this makes patch posting and reviewing more difficult. Because of this requirement to keep clean patches (which I think is fair), people using maintainers' branches can only use rebasing (or some patch management tool). > Moreover not too keen on using many tools do do one thing, so getting this > inside git itself sounded like a possibly nice notion. I don't like using many tools either, hence I use mostly StGIT :-). -- Catalin