On 2003-02-07 17:21, Peter Pentchev <[EMAIL PROTECTED]> wrote:
> On Fri, Feb 07, 2003 at 09:26:49AM -0500, Daniel Ellard wrote:
> > Something slightly broke the em (gigabit ethernet) driver between
> > 4.6.2p4 and 4.6.2p6, and I'm trying to figure what the change was so I
> > can back it out on my machine.  In 4.6.2p6 almost everything works,
> > but programs that push the device (such as netperf) can hang.  The
> > same program running on other ethernet devices (fxp, xl) works fine.
> > This happens on several machines, and they were all running correctly
> > before I updated them, so I doubt that it is a hardware problem.
> >
> > I don't see any changes for the em driver source itself between p4 and
> > p6, and the announced differences between these patch levels don't
> > look related, but something must have changed.  Is there a
> > straightforward way to track down all the source code differences
> > between p4 and p6 (or any arbitrary pair of patchlevels)?
>
> Since patchlevel bumps on the security branches are not accompanied by
> CVS tagging, the only way I can think of would be a formail-like filter
> on the messages in the commit logs, available in CVSROOT/commitlogs
> after a CVSup of the CVS repository.  The filter would have to parse the
> multi-line commit messages, and look for a (branch: RELENG_4_6) token on
> the Modified files: line.

You can always use -D 'date1' -D 'date2' with cvs diff...

For the relevant changes, I think the proper dates would be around
revisions 1.44.2.23.2.21 -> -r1.44.2.23.2.23 of the file
src/sys/conf/newvers.sh which yield the following date tags:

% cvs diff -D '2002/10/26 21:00:00 UTC' -D '2003/01/06 12:45:00 UTC'

Run this in /src and you'll find out all the changes.  I have moved
the dates slightly backward <-> forward, to catch commits that
happened in a short timeframe around the change to newvers.sh

- Giorgos


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message

Reply via email to