Hi folks,
I count 79 "Cset exclude" changelog entries since 2.5.4-pre1. Is there any
way to identify the changelog entry they revert?
for instance, "Cset exclude: [email protected]|ChangeSet|20020403195622" is in
2.5.8-pre2, as the full text of the changelog entry.
Without a way to identify the particular entry being reverted, I can't rely
on the fact that a particular changelog entry represents what actually went
into the kernel.
I realize there is almost certainly no way to directly deduce which changelog
entry is referenced by a particular 'Cset exclude' entry. But maybe there
is some *indirect* way, perhaps a website somewhere that tracks this info?
If this information isn't provided anywhere, what would be involved in
making it available? Maybe something can be done for the future.
Many thanks,
Zack
--
Zack Brown
* Zack Brown ([email protected]) wrote:
> for instance, "Cset exclude: [email protected]|ChangeSet|20020403195622" is in
> 2.5.8-pre2, as the full text of the changelog entry.
bk prs -r"[email protected]|ChangeSet|20020403195622" -hnd:REV: ChangeSet
That will give you the rev from that key in the Cset exclude message.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
Hi,
On Tue, Apr 20, 2004 at 05:26:22PM -0700, Chris Wright wrote:
> * Zack Brown ([email protected]) wrote:
> > for instance, "Cset exclude: [email protected]|ChangeSet|20020403195622" is in
> > 2.5.8-pre2, as the full text of the changelog entry.
>
> bk prs -r"[email protected]|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.
Also, I'm not allowed to license BK. Is there some other way?
Many thanks,
Zack
>
> 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 [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Zack Brown
* Zack Brown ([email protected]) wrote:
> On Tue, Apr 20, 2004 at 05:26:22PM -0700, Chris Wright wrote:
> > * Zack Brown ([email protected]) wrote:
> > > for instance, "Cset exclude: [email protected]|ChangeSet|20020403195622" is in
> > > 2.5.8-pre2, as the full text of the changelog entry.
> >
> > bk prs -r"[email protected]|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 [email protected]|ChangeSet|20020403195622 bit) in the
cvs changelog message somewhere.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
On Tue, Apr 20, 2004 at 05:26:22PM -0700, Chris Wright wrote:
> * Zack Brown ([email protected]) wrote:
> > for instance, "Cset exclude: [email protected]|ChangeSet|20020403195622" is in
> > 2.5.8-pre2, as the full text of the changelog entry.
>
> bk prs -r"[email protected]|ChangeSet|20020403195622" -hnd:REV: ChangeSet
>
> That will give you the rev from that key in the Cset exclude message.
You can use cset keys just about anywhere you can use revision numbers
in the BK interface. So,
% bk changes -r'[email protected]|ChangeSet|20020403195622'
does the right thing.
On Tue, Apr 20, 2004 at 05:38:20PM -0700, Zack Brown wrote:
> Will this give me the text of the changelog entry being reverted? That's
> what I need to find.
The "changes" command I give above will.
I'll see if I can get the "cset exclude" text to be an HREF. In the
meantime, you can construct a working URL by appending the cset key to
http://linux.bkbits.net:8080/linux-2.5/cset@
like so:
http://linux.bkbits.net:8080/linux-2.5/cset@[email protected]|ChangeSet|20020403195622
-andy
On Tue, Apr 20, 2004 at 06:02:26PM -0700, Andy Isaacson wrote:
> On Tue, Apr 20, 2004 at 05:26:22PM -0700, Chris Wright wrote:
> > * Zack Brown ([email protected]) wrote:
> > > for instance, "Cset exclude: [email protected]|ChangeSet|20020403195622" is in
> > > 2.5.8-pre2, as the full text of the changelog entry.
> >
> > bk prs -r"[email protected]|ChangeSet|20020403195622" -hnd:REV: ChangeSet
> >
> > That will give you the rev from that key in the Cset exclude message.
>
> You can use cset keys just about anywhere you can use revision numbers
> in the BK interface. So,
> % bk changes -r'[email protected]|ChangeSet|20020403195622'
> does the right thing.
>
> On Tue, Apr 20, 2004 at 05:38:20PM -0700, Zack Brown wrote:
> > Will this give me the text of the changelog entry being reverted? That's
> > what I need to find.
>
> The "changes" command I give above will.
>
> I'll see if I can get the "cset exclude" text to be an HREF. In the
That would be nice.
> meantime, you can construct a working URL by appending the cset key to
> http://linux.bkbits.net:8080/linux-2.5/cset@
>
> like so:
> http://linux.bkbits.net:8080/linux-2.5/cset@[email protected]|ChangeSet|20020403195622
This is perfect! Just what I was looking for.
Thanks Andy and Chris!
Zack
>
> -andy
> -
> 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/
--
Zack Brown