From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephan Beyer Subject: git-rebase-i migration to sequencer Date: Tue, 1 Jul 2008 04:39:26 +0200 Message-ID: <1214879968-17944-1-git-send-email-s-beyer@gmx.net> References: <1214879914-17866-5-git-send-email-s-beyer@gmx.net> Cc: Junio C Hamano , Johannes Schindelin To: git@vger.kernel.org X-From: git-owner@vger.kernel.org Tue Jul 01 04:40:37 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 1KDVnG-0005Ky-IP for gcvg-git-2@gmane.org; Tue, 01 Jul 2008 04:40:34 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756727AbYGACjh (ORCPT ); Mon, 30 Jun 2008 22:39:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756487AbYGACjf (ORCPT ); Mon, 30 Jun 2008 22:39:35 -0400 Received: from mail.gmx.net ([213.165.64.20]:54674 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1756431AbYGACje (ORCPT ); Mon, 30 Jun 2008 22:39:34 -0400 Received: (qmail invoked by alias); 01 Jul 2008 02:39:32 -0000 Received: from q137.fem.tu-ilmenau.de (EHLO leksak.fem-net) [141.24.46.137] by mail.gmx.net (mp064) with SMTP; 01 Jul 2008 04:39:32 +0200 X-Authenticated: #1499303 X-Provags-ID: V01U2FsdGVkX19IsTVeE7FIDSYWgxDnbhGU1+tRygTsD+a69/c/am EtoWeGCIZEUKL0 Received: from sbeyer by leksak.fem-net with local (Exim 4.69) (envelope-from ) id 1KDVmC-0004fr-Q8; Tue, 01 Jul 2008 04:39:28 +0200 X-Mailer: git-send-email 1.5.6.1.130.ga8860.dirty In-Reply-To: <1214879914-17866-5-git-send-email-s-beyer@gmx.net> X-Y-GMX-Trusted: 0 X-FuHaFi: 0.54 Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Hi, the patches for rebase-i migration follow. Why this intermediate mail? Because the patches will not apply to master/next/pu/whatever. It needs js/rebase-i-sequencer, that is "dropped for now" from git.git. So you have to do some extra work to apply. Well, I could've just added a "Squashed js/rebase-i-sequencer patch" or something, but 1. I didn't write the patches so I don't want to claim I'm the author, 2. It's an opportunity to try sequencer, as follows: If you still have the commits (a freshly cloned repo hasn't), you can do: git sequencer <