Tracking What it's changing in current

[Orestes Leal R.]

I need to see (with a tool or whatever) what changes have occured between  
current,
let's say between current 4.9 from february 9 and current dated february  
14.

Tracking What it's changing in current

[Orestes Leal R.]

I need to see (with a tool or whatever) what changes have occured between
current,
let's say between current 4.9 from february 9 and current dated february
14. They are logged in some place?

Re: Tracking What it's changing in current

[Orestes Leal R.]

On Tue, 15 Feb 2011 10:23:21 -0600, BSD  wrote:


On 02/15/11 10:54, Orestes Leal R. wrote:
I need to see (with a tool or whatever) what changes have occured  
between

current,
let's say between current 4.9 from february 9 and current dated february
14. They are logged in some place?



cvs


thanks ;)


--
Using Opera's revolutionary email client: http://www.opera.com/mail/

Re: Tracking What it's changing in current

[Landry Breuil]

On Tue, Feb 15, 2011 at 5:54 PM, Orestes Leal R.
 wrote:
> I need to see (with a tool or whatever) what changes have occured between
> current,
> let's say between current 4.9 from february 9 and current dated february
> 14. They are logged in some place?

Yeah, that's called CVS.

Re: Tracking What it's changing in current

[Adriaan]

On Tue, Feb 15, 2011 at 5:53 PM, Orestes Leal R.
 wrote:
> I need to see (with a tool or whatever) what changes have occured between
> current,
> let's say between current 4.9 from february 9 and current dated february 14.
>
For future changes subcribe to the "source-changes" mailing list. For
past changes see the mailing list archive of "source-changes". See
http://openbsd.org/mail.html

Re: Tracking What it's changing in current

[Luis Useche]

One thing I would really like to see is the diffs of every commit. This is
available for DragonflyBSD for instance. Is there a way to find this on
OBSD?

Luis.

On Tue, Feb 15, 2011 at 11:27 AM, Adriaan  wrote:

> On Tue, Feb 15, 2011 at 5:53 PM, Orestes Leal R.
>  wrote:
> > I need to see (with a tool or whatever) what changes have occured between
> > current,
> > let's say between current 4.9 from february 9 and current dated february
> 14.
> >
> For future changes subcribe to the "source-changes" mailing list. For
> past changes see the mailing list archive of "source-changes". See
> http://openbsd.org/mail.html

Re: Tracking What it's changing in current

[Nicolas P. M. Legrand]

On Wed, Feb 16, 2011 at 12:01:22PM -0500, Luis Useche wrote:
> One thing I would really like to see is the diffs of every commit. This is
> available for DragonflyBSD for instance. Is there a way to find this on
> OBSD?

CVS and git are very different I don't think you can easily have this
feature with CVS (if it exists I'd be glad to know it :)). Personally
I follow the commit changes on marc.info
 and use CVS tools (cvs
itself or Emacs version control) with a local source tree when I want
to see the diffs.

Re: Tracking What it's changing in current

[Nicolas P. M. Legrand]

On Wed, Feb 16, 2011 at 11:16:01AM -0800, patrick keshishian wrote:
> On Wed, Feb 16, 2011 at 10:29 AM, Nicolas P. M. Legrand
>  wrote:
> > On Wed, Feb 16, 2011 at 12:01:22PM -0500, Luis Useche wrote:
> >> One thing I would really like to see is the diffs of every commit. This is
> >> available for DragonflyBSD for instance. Is there a way to find this on
> >> OBSD?
> >
> > CVS and git are very different I don't think you can easily have this
> > feature with CVS (if it exists I'd be glad to know it :)). Personally
> 
> Sure it can. see CVSROOT/loginfo. You define a filter and need a
> filter-script that will take files with changed revisions, do the 'cvs
> diff' and mail out the outputs.

ha thanks! I'll have a look.

Re: Tracking What it's changing in current

[roberth]

On Wed, 16 Feb 2011 12:01:22 -0500
Luis Useche  wrote:

> One thing I would really like to see is the diffs of every commit.
> This is available for DragonflyBSD for instance. Is there a way to
> find this on OBSD?

that data representation is not provided by the project in the way that
you want it.

that said, cvs takes date as an argument.

yes, what you want will take some scripting elbow grease.
one could even have a button in any decent mail-client to click for
that.

if you want it on a "per commit" basis, every commit bumps the touched
files version.

if you're lazy... look at cvsweb for every file touched mentioned in
the mail on source-changes@. jup, even that is scriptable.

boils down to: just diff a checkout of the relevant files before and
after the commit.
(don't bother with anoncvs for that, mirror the tree locally, cvsync is
your friend.)

Re: Tracking What it's changing in current

[patrick keshishian]

On Wed, Feb 16, 2011 at 10:29 AM, Nicolas P. M. Legrand
 wrote:
> On Wed, Feb 16, 2011 at 12:01:22PM -0500, Luis Useche wrote:
>> One thing I would really like to see is the diffs of every commit. This is
>> available for DragonflyBSD for instance. Is there a way to find this on
>> OBSD?
>
> CVS and git are very different I don't think you can easily have this
> feature with CVS (if it exists I'd be glad to know it :)). Personally

Sure it can. see CVSROOT/loginfo. You define a filter and need a
filter-script that will take files with changed revisions, do the 'cvs
diff' and mail out the outputs.

--patrick



> I follow the commit changes on marc.info
>  and use CVS tools (cvs
> itself or Emacs version control) with a local source tree when I want
> to see the diffs.

Re: Tracking What it's changing in current

[Marco Peereboom]

Man I'd love an example for this.

On Feb 16, 2011, at 13:32, "Nicolas P. M. Legrand" 
wrote:

> On Wed, Feb 16, 2011 at 11:16:01AM -0800, patrick keshishian wrote:
>> On Wed, Feb 16, 2011 at 10:29 AM, Nicolas P. M. Legrand
>>  wrote:
>>> On Wed, Feb 16, 2011 at 12:01:22PM -0500, Luis Useche wrote:
 One thing I would really like to see is the diffs of every commit. This
is
 available for DragonflyBSD for instance. Is there a way to find this on
 OBSD?
>>>
>>> CVS and git are very different I don't think you can easily have this
>>> feature with CVS (if it exists I'd be glad to know it :)). Personally
>>
>> Sure it can. see CVSROOT/loginfo. You define a filter and need a
>> filter-script that will take files with changed revisions, do the 'cvs
>> diff' and mail out the outputs.
>
> ha thanks! I'll have a look.

Re: Tracking What it's changing in current

[Landry Breuil]

On Wed, Feb 16, 2011 at 6:01 PM, Luis Useche  wrote:
> One thing I would really like to see is the diffs of every commit. This is
> available for DragonflyBSD for instance. Is there a way to find this on
> OBSD?

http://anoncvs.estpak.ee/cgi-bin/cgit/

Re: Tracking What it's changing in current

[joshua stein]

> >> One thing I would really like to see is the diffs of every commit. This is
> >> available for DragonflyBSD for instance. Is there a way to find this on
> >> OBSD?
> >
> > CVS and git are very different I don't think you can easily have this
> > feature with CVS (if it exists I'd be glad to know it :)). Personally
> 
> Sure it can. see CVSROOT/loginfo. You define a filter and need a
> filter-script that will take files with changed revisions, do the 'cvs
> diff' and mail out the outputs.

that's for running things when commits happen, but not for
generating diffs from a tree after the fact.

(a loginfo script to send diffs/cvsweb urls is at
https://github.com/jcs/cvs-loginfo/blob/master/loginfo.pl)

if you want to generate a single changeset/diff of a commit (which
cvs doesn't support natively), you can use devel/cvsps in the ports
tree to run on a checked-out tree.

Re: Tracking What it's changing in current

[Andres Perera]

On Wed, Feb 16, 2011 at 4:31 PM, Marco Peereboom  wrote:
> On Feb 16, 2011, at 13:32, "Nicolas P. M. Legrand" 
> wrote:
>> On Wed, Feb 16, 2011 at 11:16:01AM -0800, patrick keshishian wrote:
>>> On Wed, Feb 16, 2011 at 10:29 AM, Nicolas P. M. Legrand
>>>  wrote:
 On Wed, Feb 16, 2011 at 12:01:22PM -0500, Luis Useche wrote:
> One thing I would really like to see is the diffs of every commit. This
> is
> available for DragonflyBSD for instance. Is there a way to find this on
> OBSD?

 CVS and git are very different I don't think you can easily have this
 feature with CVS (if it exists I'd be glad to know it :)). Personally
>>>
>>> Sure it can. see CVSROOT/loginfo. You define a filter and need a
>>> filter-script that will take files with changed revisions, do the 'cvs
>>> diff' and mail out the outputs.
>>
>> ha thanks! I'll have a look.
>
> Man I'd love an example for this.

loginfo would work comfortably only if the commits are in one
directory, since it runs once per dir:


andres@pote:~/tmp $ awk 'length && !/^#/' CVSROOT/loginfo
ALL ~/tmp/loginfo.sh %{sVv}


andres@pote:~/tmp $ cat loginfo.sh
#!/bin/sh

echo -- LOGINFO ARGC: "$#"
echo -- LOGINFO ARGV: "$@"
echo -- LOGINFO STDIN:
cat
echo -- LOGINFO EOF


andres@pote:~/tmp $ cvs ci -m'test' b CVSROOT
/home/andres/tmp/cvstmp/b,v  <--  b
new revision: 1.5; previous revision: 1.4
-- LOGINFO ARGC: 1
-- LOGINFO ARGV:
-- LOGINFO STDIN:
Update of /home/andres/tmp/cvstmp
In directory pote.domain.local:/home/andres/tmp

Modified Files:
b
Log Message:
test
-- LOGINFO EOF
/home/andres/tmp/cvstmp/CVSROOT/loginfo,v  <--  CVSROOT/loginfo
new revision: 1.8; previous revision: 1.7
cvs commit: Rebuilding administrative file database
-- LOGINFO ARGC: 3
-- LOGINFO ARGV: loginfo 1.7 1.8
-- LOGINFO STDIN:
Update of /home/andres/tmp/cvstmp/CVSROOT
In directory pote.domain.local:/home/andres/tmp/CVSROOT

Modified Files:
loginfo
Log Message:
test
-- LOGINFO EOF

Re: Tracking What it's changing in current

[Martin Schröder]

2011/2/16 Nicolas P. M. Legrand :
> CVS and git are very different I don't think you can easily have this
> feature with CVS (if it exists I'd be glad to know it :)). Personally

This already worked the last millenium (probably some guy in Finland
started working on an OS).

Best
   Martin

Re: Tracking What it's changing in current

[Marco Peereboom]

Is it possible to catch the entire commit and have that diff generated?

On Wed, Feb 16, 2011 at 05:50:13PM -0430, Andres Perera wrote:
> On Wed, Feb 16, 2011 at 4:31 PM, Marco Peereboom  wrote:
> > On Feb 16, 2011, at 13:32, "Nicolas P. M. Legrand" 
> > wrote:
> >> On Wed, Feb 16, 2011 at 11:16:01AM -0800, patrick keshishian wrote:
> >>> On Wed, Feb 16, 2011 at 10:29 AM, Nicolas P. M. Legrand
> >>>  wrote:
>  On Wed, Feb 16, 2011 at 12:01:22PM -0500, Luis Useche wrote:
> > One thing I would really like to see is the diffs of every commit. This
> > is
> > available for DragonflyBSD for instance. Is there a way to find this on
> > OBSD?
> 
>  CVS and git are very different I don't think you can easily have this
>  feature with CVS (if it exists I'd be glad to know it :)). Personally
> >>>
> >>> Sure it can. see CVSROOT/loginfo. You define a filter and need a
> >>> filter-script that will take files with changed revisions, do the 'cvs
> >>> diff' and mail out the outputs.
> >>
> >> ha thanks! I'll have a look.
> >
> > Man I'd love an example for this.
> 
> loginfo would work comfortably only if the commits are in one
> directory, since it runs once per dir:
> 
> 
> andres@pote:~/tmp $ awk 'length && !/^#/' CVSROOT/loginfo
> ALL ~/tmp/loginfo.sh %{sVv}
> 
> 
> andres@pote:~/tmp $ cat loginfo.sh
> #!/bin/sh
> 
> echo -- LOGINFO ARGC: "$#"
> echo -- LOGINFO ARGV: "$@"
> echo -- LOGINFO STDIN:
> cat
> echo -- LOGINFO EOF
> 
> 
> andres@pote:~/tmp $ cvs ci -m'test' b CVSROOT
> /home/andres/tmp/cvstmp/b,v  <--  b
> new revision: 1.5; previous revision: 1.4
> -- LOGINFO ARGC: 1
> -- LOGINFO ARGV:
> -- LOGINFO STDIN:
> Update of /home/andres/tmp/cvstmp
> In directory pote.domain.local:/home/andres/tmp
> 
> Modified Files:
> b
> Log Message:
> test
> -- LOGINFO EOF
> /home/andres/tmp/cvstmp/CVSROOT/loginfo,v  <--  CVSROOT/loginfo
> new revision: 1.8; previous revision: 1.7
> cvs commit: Rebuilding administrative file database
> -- LOGINFO ARGC: 3
> -- LOGINFO ARGV: loginfo 1.7 1.8
> -- LOGINFO STDIN:
> Update of /home/andres/tmp/cvstmp/CVSROOT
> In directory pote.domain.local:/home/andres/tmp/CVSROOT
> 
> Modified Files:
> loginfo
> Log Message:
> test
> -- LOGINFO EOF

Re: Tracking What it's changing in current

[patrick keshishian]

On Wed, Feb 16, 2011 at 1:01 PM, Marco Peereboom  wrote:
> Man I'd love an example for this.

something like this. Note that there may be issues with source files
with spaces and/or files names that contain commas. Those cases are
not tested. The script can be "smarter".

# -- BEGIN
CVSROOT/loginfo:

# Some info from: http://www.network-theory.co.uk/docs/cvsmanual/loginfo.html

# Format of each line is:
# regular-expressionfilter-program args [...]
#
# pattern to match against directory entry being changed.
# So if your repository is something generic like OpenBSD's
# "src", you probably want to use "^src"
#
# The filter script/program to execute comes next with arguments.
# Part of the arguments can be a format string where:
#
#   %s is the file name being changed
#   %t tag name
#   %V old revision number (pre-check-in)
#   %v new revision number (post)
#
# Multiple format chars may be used but must be enclosed within
# curly-braces (e.g., %{sVv}).
#
# The format string will expand to:
#
#   "repository-subdir format-specifier-list-of-changed-files"
#
# e.g., If the repository is the OpenBSD "src" and the change is
# made to sys/dev/pci/azalia.c and sys/dev/pci/azalia.h, and the
# format specifier is "%{sVv}", the first argument to filter-program
# will be:
#
#   "sys/dev/pci azalia.c,1.187,1.188 azalia.h,1.61,1.62"
#
# Assuming azalia.c is at rev 1.187 and azalia.h is at 1.61.

^src/path/to/filter.pl %{sVv}


# So your filter.pl may be something like:

#! /usr/bin/perl -w
#
# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHORS DISCLAIM ALL WARRANTIES
# WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
# MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR
# ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
# WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
# ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
# OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

use strict;

# Assumes CVSROOT env is set correctly.

my  ($mail, $subdir, @files, @email);

# XXX FIXME!
# Adjust mailing list here, or make it part of params in the loginfo
# filter line as an additional arg to filter-program.
@email = qw{sl...@example.com nlegr...@example.com
m...@example.com};

# First arge is "sub-dir fileschanged,old-rev,new-rev ..."
($subdir, @files) = split(/ /, $ARGV[0]);

# Send email to @email list
$mail = sprintf("mail -s \"cvs: changes in %s\" ", $subdir);
$mail .= join(',', @email);

open(MAIL, "| $mail") or die("Failed to open mail: $!");

# Need to read input from 'cvs commit'. Send it as the mail message.
while () {
print(MAIL $_);
}

# Do cvs diffs for each changed file.
for my $f (@files) {
my  ($o, $old, $new, $src);

($src, $old, $new) = split(/,/, $f);

print(MAIL "\n-- diff -r$old -r$new $src --\n");
$o = qx{cvs -nq diff -up -r$old -r$new $src};
print(MAIL "$o\n");
}

close(MAIL);
# -- END

enjoy,
--patrick




> On Feb 16, 2011, at 13:32, "Nicolas P. M. Legrand"  
> wrote:
>
>> On Wed, Feb 16, 2011 at 11:16:01AM -0800, patrick keshishian wrote:
>>> On Wed, Feb 16, 2011 at 10:29 AM, Nicolas P. M. Legrand
>>>  wrote:
 On Wed, Feb 16, 2011 at 12:01:22PM -0500, Luis Useche wrote:
> One thing I would really like to see is the diffs of every commit. This is
> available for DragonflyBSD for instance. Is there a way to find this on
> OBSD?

 CVS and git are very different I don't think you can easily have this
 feature with CVS (if it exists I'd be glad to know it :)). Personally
>>>
>>> Sure it can. see CVSROOT/loginfo. You define a filter and need a
>>> filter-script that will take files with changed revisions, do the 'cvs
>>> diff' and mail out the outputs.
>>
>> ha thanks! I'll have a look.

Re: Tracking What it's changing in current

[Andres Perera]

sent to a patrick only by mistake

-- Forwarded message --
From: Andres Perera 
Date: Wed, Feb 16, 2011 at 8:58 PM
Subject: Re: Tracking What it's changing in current
To: patrick keshishian 


On Wed, Feb 16, 2011 at 7:03 PM, patrick keshishian 
wrote:
> On Wed, Feb 16, 2011 at 1:01 PM, Marco Peereboom 
wrote:
>> Man I'd love an example for this.
>
> something like this. Note that there may be issues with source files
> with spaces and/or files names that contain commas. Those cases are
> not tested. The script can be "smarter".
>


this will still run per directory instead of per commit:

andres@pote:/tmp/andres/CVSROOT $ awk 'length && !/^#/' loginfo commitinfo
ALL echo LOGINFO %s
ALL echo COMMITINFO %s

andres@pote:/tmp/andres/foo $ for i in bar kjh/lal qweqweqwe; do echo
\# >> $i; done
andres@pote:/tmp/andres/foo $ cvs -n up
M bar
M qweqweqwe
M kjh/lal
andres@pote:/tmp/andres/foo $ cvs ci -masdasd .
COMMITINFO bar qweqweqwe
COMMITINFO lal
/tmp/andres/asd/foo/bar,v B <-- B bar
new revision: 1.16; previous revision: 1.15
/tmp/andres/asd/foo/qweqweqwe,v B <-- B qweqweqwe
new revision: 1.10; previous revision: 1.9
LOGINFO bar qweqweqwe
/tmp/andres/asd/foo/kjh/lal,v B <-- B kjh/lal
new revision: 1.16; previous revision: 1.15
LOGINFO lal

i am trying to see if CVSROOT/modules could work (with a line like
`modname -i command modname'), but i doubt it. and then there's the
whole clientside/serverside depending on whether CVSROOT is nfs or
pserver... etc.

cant test CVSROOT/modules atm because im not on an openbsd box, nor do
i have old cvs

Re: Tracking What it's changing in current

[Marco Peereboom]

Right, but that is the holy grail because now you'd have change sets.

I'll pay prize money for that ;-)

On Thu, Feb 17, 2011 at 06:13:32AM -0800, patrick keshishian wrote:
> On Thu, Feb 17, 2011 at 6:05 AM, Christiano F. Haesbaert
>  wrote:
> > On 16 February 2011 22:21, Marco Peereboom  wrote:
> >> Is it possible to catch the entire commit and have that diff generated?
> >>
> >
> > I'm a little late at this thread but yes, we do that here in work.
> > Don't have access to the scripts though :(
> 
> he means a commit that touches files in multiple directory locations
> throughout a source tree. I'm not sure if this is possible so easily.
> 
> --patrick

Re: Tracking What it's changing in current

[Christiano F. Haesbaert]

On 16 February 2011 22:21, Marco Peereboom  wrote:
> Is it possible to catch the entire commit and have that diff generated?
>

I'm a little late at this thread but yes, we do that here in work.
Don't have access to the scripts though :(

Re: Tracking What it's changing in current

[Darrin Chandler]

IIRC, someone had methods to import CVS into Mercurial (hg) using cvsps that
largely succeeded in making change sets. Of course it's not perfect, but
it can never be perfect. It's been too long for me to remember details.

On Thu, Feb 17, 2011 at 09:01:20AM -0600, Marco Peereboom wrote:
> Right, but that is the holy grail because now you'd have change sets.
> 
> I'll pay prize money for that ;-)
> 
> On Thu, Feb 17, 2011 at 06:13:32AM -0800, patrick keshishian wrote:
> > On Thu, Feb 17, 2011 at 6:05 AM, Christiano F. Haesbaert
> >  wrote:
> > > On 16 February 2011 22:21, Marco Peereboom  wrote:
> > >> Is it possible to catch the entire commit and have that diff generated?
> > >>
> > >
> > > I'm a little late at this thread but yes, we do that here in work.
> > > Don't have access to the scripts though :(
> > 
> > he means a commit that touches files in multiple directory locations
> > throughout a source tree. I'm not sure if this is possible so easily.
> > 
> > --patrick
> 

-- 
You've been warned.

Re: Tracking What it's changing in current

[patrick keshishian]

On Thu, Feb 17, 2011 at 6:05 AM, Christiano F. Haesbaert
 wrote:
> On 16 February 2011 22:21, Marco Peereboom  wrote:
>> Is it possible to catch the entire commit and have that diff generated?
>>
>
> I'm a little late at this thread but yes, we do that here in work.
> Don't have access to the scripts though :(

he means a commit that touches files in multiple directory locations
throughout a source tree. I'm not sure if this is possible so easily.

--patrick

Re: Tracking What it's changing in current

[Dan Brosemer]

Am I missing something, or is this what you're looking for?
http://cleannorth.org/lists/archive/cvs/2011-02/msg00022.html

If so, it's generated by:
http://search.cpan.org/dist/activitymail/bin/activitymail

-Dan

On Thu, Feb 17, 2011 at 09:01:20AM -0600, Marco Peereboom wrote:
> Right, but that is the holy grail because now you'd have change sets.
> 
> I'll pay prize money for that ;-)
> 
> On Thu, Feb 17, 2011 at 06:13:32AM -0800, patrick keshishian wrote:
> > On Thu, Feb 17, 2011 at 6:05 AM, Christiano F. Haesbaert
> >  wrote:
> > > On 16 February 2011 22:21, Marco Peereboom  wrote:
> > >> Is it possible to catch the entire commit and have that diff generated?
> > >>
> > >
> > > I'm a little late at this thread but yes, we do that here in work.
> > > Don't have access to the scripts though :(
> > 
> > he means a commit that touches files in multiple directory locations
> > throughout a source tree. I'm not sure if this is possible so easily.
> > 
> > --patrick

Re: Tracking What it's changing in current

[Marco Peereboom]

Yeah that is exactly what I'd want!

On Thu, Feb 17, 2011 at 04:42:15PM -0200, Christiano F. Haesbaert wrote:
> On 17 February 2011 12:13, patrick keshishian  wrote:
> > On Thu, Feb 17, 2011 at 6:05 AM, Christiano F. Haesbaert
> >  wrote:
> >> On 16 February 2011 22:21, Marco Peereboom  wrote:
> >>> Is it possible to catch the entire commit and have that diff generated?
> >>>
> >>
> >> I'm a little late at this thread but yes, we do that here in work.
> >> Don't have access to the scripts though :(
> >
> > he means a commit that touches files in multiple directory locations
> > throughout a source tree. I'm not sure if this is possible so easily.
> >
> 
> Yep, we have that, the guy who manages that here is on holidays, when
> he comes back I'll see if I can get it.
> 
> Module: 
> 
> Log Message:
> foo bar
> 
> Files:
> //PC.h : 1.48 -> 1.49
> //apps/Y : 1.2 -> 1.3
> 
> -- follows both diffs --
> 
> Is that it ?

Re: Tracking What it's changing in current

[Christiano F. Haesbaert]

On 17 February 2011 16:45, Marco Peereboom  wrote:
> Yeah that is exactly what I'd want!
>


I did some quick digging, it seems we use this stuff:

http://www.infodrom.org/Infodrom/tools/cvs-mailcommit.html

Re: Tracking What it's changing in current

[Christiano F. Haesbaert]

On 17 February 2011 12:13, patrick keshishian  wrote:
> On Thu, Feb 17, 2011 at 6:05 AM, Christiano F. Haesbaert
>  wrote:
>> On 16 February 2011 22:21, Marco Peereboom  wrote:
>>> Is it possible to catch the entire commit and have that diff generated?
>>>
>>
>> I'm a little late at this thread but yes, we do that here in work.
>> Don't have access to the scripts though :(
>
> he means a commit that touches files in multiple directory locations
> throughout a source tree. I'm not sure if this is possible so easily.
>

Yep, we have that, the guy who manages that here is on holidays, when
he comes back I'll see if I can get it.

Module: 

Log Message:
foo bar

Files:
//PC.h : 1.48 -> 1.49
//apps/Y : 1.2 -> 1.3

-- follows both diffs --

Is that it ?

Re: Tracking What it's changing in current

[Andres Perera]

On Thu, Feb 17, 2011 at 2:05 PM, Dan Brosemer  wrote:
> On Thu, Feb 17, 2011 at 09:01:20AM -0600, Marco Peereboom wrote:
>> Right, but that is the holy grail because now you'd have change sets.
>> On Thu, Feb 17, 2011 at 06:13:32AM -0800, patrick keshishian wrote:
>> > On Thu, Feb 17, 2011 at 6:05 AM, Christiano F. Haesbaert
>> >  wrote:
>> > > On 16 February 2011 22:21, Marco Peereboom  wrote:
>> > >> Is it possible to catch the entire commit and have that diff generated?
>> > >>
>> > >
>> > > I'm a little late at this thread but yes, we do that here in work.
>> > > Don't have access to the scripts though :(
>> >
>> > he means a commit that touches files in multiple directory locations
>> > throughout a source tree. I'm not sure if this is possible so easily.
>> >
>> > --patrick
>>
>> I'll pay prize money for that ;-)
>
> Am I missing something, or is this what you're looking for?
> http://cleannorth.org/lists/archive/cvs/2011-02/msg00022.html
>
> If so, it's generated by:
> http://search.cpan.org/dist/activitymail/bin/activitymail

looking at their gitrepo:
https://github.com/theory/activitymail/blob/master/bin/activitymail

it parses stdin to determine which is the last dir modified in the commit,
copying each invocation to a tmpfile before concat/sending them

it works but i don't like the fact that it's working around cvs

Re: Tracking What it's changing in current

[Luis Useche]

I would love this feature in OpenBSD src list. Is it possible to use the
activitymail script on the OpenBSD CVS repo?

Luis.

On Thu, Feb 17, 2011 at 1:59 PM, Andres Perera  wrote:

> On Thu, Feb 17, 2011 at 2:05 PM, Dan Brosemer 
> wrote:
> > On Thu, Feb 17, 2011 at 09:01:20AM -0600, Marco Peereboom wrote:
> >> Right, but that is the holy grail because now you'd have change sets.
> >> On Thu, Feb 17, 2011 at 06:13:32AM -0800, patrick keshishian wrote:
> >> > On Thu, Feb 17, 2011 at 6:05 AM, Christiano F. Haesbaert
> >> >  wrote:
> >> > > On 16 February 2011 22:21, Marco Peereboom 
> wrote:
> >> > >> Is it possible to catch the entire commit and have that diff
> generated?
> >> > >>
> >> > >
> >> > > I'm a little late at this thread but yes, we do that here in work.
> >> > > Don't have access to the scripts though :(
> >> >
> >> > he means a commit that touches files in multiple directory locations
> >> > throughout a source tree. I'm not sure if this is possible so easily.
> >> >
> >> > --patrick
> >>
> >> I'll pay prize money for that ;-)
> >
> > Am I missing something, or is this what you're looking for?
> > http://cleannorth.org/lists/archive/cvs/2011-02/msg00022.html
> >
> > If so, it's generated by:
> > http://search.cpan.org/dist/activitymail/bin/activitymail
>
> looking at their gitrepo:
> https://github.com/theory/activitymail/blob/master/bin/activitymail
>
> it parses stdin to determine which is the last dir modified in the commit,
> copying each invocation to a tmpfile before concat/sending them
>
> it works but i don't like the fact that it's working around cvs

Re: Tracking What it's changing in current

[Andres Perera]

On Mon, Feb 21, 2011 at 10:38 AM, Luis Useche  wrote:
>
> On Thu, Feb 17, 2011 at 1:59 PM, Andres Perera  wrote:
>>
>> looking at their gitrepo:
>> https://github.com/theory/activitymail/blob/master/bin/activitymail
>>
>> it parses stdin to determine which is the last dir modified in the commit,
>> copying each invocation to a tmpfile before concat/sending them
>>
>> it works but i don't like the fact that it's working around cvs
>
> I would love this feature in OpenBSD src list. Is it possible to use the
> activitymail script on the OpenBSD CVS repo?
>

it has to be used by the server, the same way source-changes@ works

although i would prefer they didn't do that since all the scripts on
this thread are hacky

it would be better if cvs itself could trigger per commit instead of per dir

Re: Tracking What it's changing in current

[Andres Perera]

On Mon, Feb 21, 2011 at 12:58 PM, Andres Perera  wrote:
>
> it has to be used by the server, the same way source-changes@ works
>

actually, disregard that

i've no idea wtf they use but it's not necessarily serverside as far
as i can see

Re: Tracking What it's changing in current

[Ted Unangst]

On Mon, Feb 21, 2011 at 10:08 AM, Luis Useche  wrote:
> I would love this feature in OpenBSD src list. Is it possible to use the
> activitymail script on the OpenBSD CVS repo?

seems like a serious waste of bandwidth.  If you care about seeing the
diffs often enough that checking things out in cvsweb is a hassle,
just start mirroring the cvs repo yourself.

Re: Tracking What it's changing in current

[Luis Useche]

On Mon, Feb 21, 2011 at 2:31 PM, Ted Unangst  wrote:

> On Mon, Feb 21, 2011 at 10:08 AM, Luis Useche  wrote:
> > I would love this feature in OpenBSD src list. Is it possible to use the
> > activitymail script on the OpenBSD CVS repo?
>
> seems like a serious waste of bandwidth.  If you care about seeing the
> diffs often enough that checking things out in cvsweb is a hassle,
> just start mirroring the cvs repo yourself.
>

Fair enough.

Another solution is to append the URL with the diff in the cvsweb like the
guys on dragonflybsd do. For example:
http://leaf.dragonflybsd.org/mailarchive/commits/2011-02/msg0.html.

BTW, I guess I am not smart enough, but I haven't been able to find this
information from the cvsweb.

Luis

Re: Tracking What it's changing in current

[Andres Perera]

On Mon, Feb 21, 2011 at 3:27 PM, Luis Useche  wrote:
> On Mon, Feb 21, 2011 at 2:31 PM, Ted Unangst  wrote:
>
>> On Mon, Feb 21, 2011 at 10:08 AM, Luis Useche  wrote:
>> > I would love this feature in OpenBSD src list. Is it possible to use the
>> > activitymail script on the OpenBSD CVS repo?
>>
>> seems like a serious waste of bandwidth. B If you care about seeing the
>> diffs often enough that checking things out in cvsweb is a hassle,
>> just start mirroring the cvs repo yourself.
>>

no, some scripts append the commands instead of the diffs themselves, so
there's no bandwidth waste:

 [...]

 Log message:
 oh well, letbs give it a manpage

 also, macro-ise Makefile and prepare for things like ambstowcs(3)b&

 To generate a diff of this changeset, execute the following commands:
 cvs -R rdiff -kk -upr1.57 -r1.58 src/distrib/lists/base/dev/mi
 cvs -R rdiff -kk -upr1.1 -r1.2 src/lib/libmbfun/Makefile
 cvs -R rdiff -kk -upr0 -r1.1 src/lib/libmbfun/cdblockedread.3

>
> Fair enough.
>
> Another solution is to append the URL with the diff in the cvsweb like the
> guys on dragonflybsd do. For example:
> http://leaf.dragonflybsd.org/mailarchive/commits/2011-02/msg0.html.
>
> BTW, I guess I am not smart enough, but I haven't been able to find this
> information from the cvsweb.

no, you can't get a changeset from http://www.openbsd.org/cgi-bin/cvsweb/

only diffs per file

>
> Luis

Re: Tracking What it's changing in current

[Ted Unangst]

On Mon, Feb 21, 2011 at 2:57 PM, Luis Useche  wrote:
> Another solution is to append the URL with the diff in the cvsweb like the
> guys on dragonflybsd do. For example:
> http://leaf.dragonflybsd.org/mailarchive/commits/2011-02/msg0.html.
>
> BTW, I guess I am not smart enough, but I haven't been able to find this
> information from the cvsweb.

That's because cvsweb is not git.

Re: Tracking What it's changing in current

[Stuart Henderson]

On 2011-02-15, Orestes Leal R.  wrote:
> I need to see (with a tool or whatever) what changes have occured between  
> current, let's say between current 4.9 from february 9 and current dated
> february 14.

here are some options:

cvsps (in packages)
http://anoncvs.estpak.ee/cgi-bin/cgit/openbsd-src/
http://www.squish.net/openbsd/

Re: Tracking What it's changing in current

[Joachim Schipper]

On Mon, Feb 21, 2011 at 02:31:20PM -0500, Ted Unangst wrote:
> On Mon, Feb 21, 2011 at 10:08 AM, Luis Useche  wrote:
> > I would love this feature in OpenBSD src list. Is it possible to use the
> > activitymail script on the OpenBSD CVS repo?
> 
> seems like a serious waste of bandwidth.  If you care about seeing the
> diffs often enough that checking things out in cvsweb is a hassle,
> just start mirroring the cvs repo yourself.

I think it would be useful, and I'd expect source-changes to have so few
subscribers that the extra bandwidth use would be dwarfed by any of the
usual misc@ nonsense threads. I'd be happy to be proven wrong, though,
and you should, of course, feel free to ignore me.

Joachim

-- 
PotD: databases/ruby-kirbybase - small, plain-text, DBMS written in Ruby
http://www.joachimschipper.nl/