Messages in this thread | | | Date | Tue, 20 Apr 2004 17:41:47 -0700 | From | Chris Wright <> | Subject | Re: matching "Cset exclude" changelog entries to the changelog entries they revert. |
| |
* Zack Brown (zbrown@tumblerings.org) wrote: > On Tue, Apr 20, 2004 at 05:26:22PM -0700, Chris Wright wrote: > > * Zack Brown (zbrown@tumblerings.org) wrote: > > > for instance, "Cset exclude: davej@suse.de|ChangeSet|20020403195622" is in > > > 2.5.8-pre2, as the full text of the changelog entry. > > > > bk prs -r"davej@suse.de|ChangeSet|20020403195622" -hnd:REV: ChangeSet > > > > That will give you the rev from that key in the Cset exclude message. > > Will this give me the text of the changelog entry being reverted? That's > what I need to find.
This would give you a revision nubmer like: 1.369.104.61. So you could then do bk changes -r1.369.104.61 to see the changelog entry.
> Also, I'm not allowed to license BK. Is there some other way?
Ugh. I can't think of any, unless the bk->cvs gateway puts the ChangeSet Key (the davej@suse.de|ChangeSet|20020403195622 bit) in the cvs changelog message somewhere.
thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |