On 7/2/07, Alex Riesen <[email protected]> wrote:
In that second case I can only suspect that all your branches point at the same commit, which is just before the one the file was removed in...
_Not_ the same. Just some commit before the file was removed, of course. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- why does git perpetually complain about include/asm-blackfin/macros.h?
- From: "Robert P. J. Day" <[email protected]>
- Re: why does git perpetually complain about include/asm-blackfin/macros.h?
- From: Jeff Garzik <[email protected]>
- Re: why does git perpetually complain about include/asm-blackfin/macros.h?
- From: "Jesper Juhl" <[email protected]>
- Re: why does git perpetually complain about include/asm-blackfin/macros.h?
- From: Jeff Garzik <[email protected]>
- Re: why does git perpetually complain about include/asm-blackfin/macros.h?
- From: "Alex Riesen" <[email protected]>
- why does git perpetually complain about include/asm-blackfin/macros.h?
- Prev by Date: Re: why does git perpetually complain about include/asm-blackfin/macros.h?
- Next by Date: Re: [2.6 patch] sound/pci/hda/patch_realtek.c: remove dead code
- Previous by thread: Re: why does git perpetually complain about include/asm-blackfin/macros.h?
- Next by thread: Re: why does git perpetually complain about include/asm-blackfin/macros.h?
- Index(es):