From: Linus Torvalds Date: Mon, 13 Feb 2006 16:44:42 GMT Subject: Re: git-bisect problem Message-ID: In-Reply-To: <20060213022527.3f888666.akpm@osdl.org> On Mon, 13 Feb 2006, Andrew Morton wrote: > Ryan Anderson wrote: > > > > git format-patch -o ~/a 386093ef9a6c88576d8b418bf1c8616d5e410a20^1..386093ef9a6c88576d8b418bf1c8616d5e410a20 > > That worked. Well, really, it's much nicer these days to just say git show 386093ef9 and you're done. For me, it gives a nice diff-tree 386093ef9a6c88576d8b418bf1c8616d5e410a20 (from ce5f8d70ba6e3d7ffcaff86b2cf91a42c27f77af) Author: Alexey Dobriyan Date: Wed Feb 1 03:04:57 2006 -0800 [PATCH] ipw2200: fix ->eeprom[EEPROM_VERSION] check priv->eeprom is a pointer. Signed-off-by: Alexey Dobriyan Acked-by: Yi Zhu Cc: James Ketrenos Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds diff --git a/drivers/net/wireless/ipw2200.c b/drivers/net/wireless/ipw2200.c index 916b24c..14beab4 100644 --- a/drivers/net/wireless/ipw2200.c +++ b/drivers/net/wireless/ipw2200.c @@ -2456,7 +2456,7 @@ static void ipw_eeprom_init_sram(struct copy. Otherwise let the firmware know to perform the operation on it's own */ - if ((priv->eeprom + EEPROM_VERSION) != 0) { + if (priv->eeprom[EEPROM_VERSION] != 0) { IPW_DEBUG_INFO("Writing EEPROM data into SRAM\n"); /* write the eeprom data to sram */ which looks sane. > I'm still not having much success geting a string of patches out of it. > > git format-patch -o ~/a d834a41c966c6a20368fadb59248740935e6fbae..826eeb53a6f264842200d3311d69107d2eb25f5e well, that's 1003 patches you're asking for. That's almost certainly _not_ what you want. Do "gitk ..args.." to visually see what you're doing. Or, what I did: git-rev-list d834a41c966c6a20368fadb59248740935e6fbae..826eeb53a6f264842200d3311d69107d2eb25f5e | wc -l which is how I got the 1003. I'm pretty sure it wasn't what you meant to do. > How do I get the IPW patches out of Jeff's tree, in order? > > I guess since I found a command which actually works, I can type that > 20-odd times. "git show". Much simpler. HOWEVER. Doing that 20-odd times sounds insane. Just use gitk to see that you actually have the right starting and ending points. Visualizing the history really is very important. If you had tried gitk, you'd have immediately seen what you were doing, and that it wasn't what you wanted. Only after you're really comfortable with git should you do anything at all without looking at it visually first. (After you've done that a few months, you won't need it any more - your brain will be able to visualize things on its own. gitk is just the training wheels). Linus