On Sun, 12 Jan 2003, Jaroslav Kysela wrote: > > You can import this changeset into BK by piping this whole message to: > '| bk receive [path to repository]' or apply the patch as usual. STOP THIS F*CKING MADNESS ALREADY. If you send BK patches, at least do it right, and make sure your BK patch is a proper child of something I actually _have_, so that I don't get results like: takepatch: can't find parent ID perex _at_ suse.cz|ChangeSet|20030111100546|48939 in RESYNC/SCCS/s.ChangeSet and if you only want to send the patch and not use BK merges, then don't even bother to _use_ the BK merge stuff. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [PATCH] PnP update - driversJaroslav Kysela
- Prev by Date: Re: any chance of 2.6.0-test*?
- Next by Date: Re: Intel And Kenrel Programming (was: Nvidia is a great company)
- Previous by thread: [PATCH] Linux PnP Support 0.94 by Adam Belay
- Next by thread: Re: [PATCH] PnP update - drivers
- Indexes:[Main][Thread]