On Tue, May 18, 2004 at 08:43:33PM +0200, Andreas Kohn wrote:
cvs can't provide you with that kind of information, because it doesn't
remember it (cvs works on file-by-file base). But, it can tell you when
the 1.337 commit to vfs_syscalls.c happened.
...
You can then use the archive of
On Friday 28 May 2004 01:01 pm, Kevin A. Pieckiel wrote:
On Tue, May 18, 2004 at 08:43:33PM +0200, Andreas Kohn wrote:
cvs can't provide you with that kind of information, because it
doesn't remember it (cvs works on file-by-file base). But, it can
tell you when the 1.337 commit to
On Fri, May 28, 2004 at 02:20:45PM -0700, Kent Stewart wrote:
The history is always available using cvsweb.cgi such as
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/kern/vfs_syscalls.c
Back up to the top and bookmark it.
Also has the alias http://cvsweb.freebsd.org/
Kris
On Mon, 2004-05-17 at 21:27, Kevin A. Pieckiel wrote:
I have a system running the latest sources via CVS in the RELENG_5_2
branch. I want to update sys/kernel/vfs_syscalls.c from version 1.333
(which is the latest available in this branch) to version 1.346 from
HEAD. The problem is that the
I have a system running the latest sources via CVS in the RELENG_5_2
branch. I want to update sys/kernel/vfs_syscalls.c from version 1.333
(which is the latest available in this branch) to version 1.346 from
HEAD. The problem is that the commit for version 1.337 modified more
than one file--some
