From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by ozlabs.org (Postfix) with ESMTP id AADEDDDDD6 for ; Sun, 9 Dec 2007 17:22:04 +1100 (EST) Received: by an-out-0708.google.com with SMTP id c37so279777anc for ; Sat, 08 Dec 2007 22:22:03 -0800 (PST) Message-ID: Date: Sat, 8 Dec 2007 23:22:03 -0700 From: "Grant Likely" Sender: glikely@secretlab.ca To: "Jerry Van Baren" Subject: Re: Stupid git question: adding acked-by In-Reply-To: <475B7B41.4000505@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 References: <475B7B41.4000505@gmail.com> Cc: "linuxppc-dev@ozlabs.org" List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 12/8/07, Jerry Van Baren wrote: > Stacked git should work (effectively does the same thing but more > gracefully), but I have not gone that route yet. This is my preferred solution, but you don't have to do it this way. > > There must be a better way, if only I could find the right (of 137) > git-* command... Try git-cherry-pick. Get a list of the SHA-1 patch ids and reset your branch. Then cherry pick each patch with the -e flag. Git will pull up an editor and let you edit the commit message before applying so you can add the Acked-by line. Cheers, g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. grant.likely@secretlab.ca (403) 399-0195