From: Johannes Stezenbach <js@convergence.de>
To: Jun Sun <jsun@mvista.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [ANNOUNCE] "cvs explorer" for linux-mips CVS tree
Date: Thu, 5 Feb 2004 19:40:08 +0100 [thread overview]
Message-ID: <20040205184008.GC13068@convergence.de> (raw)
In-Reply-To: <20040204150820.H26726@mvista.com>
Jun Sun wrote:
>
> I wrote a CVS tracking tool that tracks CVS changes in patch format
> and present them with a web interface. It is now set up to track
> linux-mips.org tree at the following place. Enjoy.
>
> http://www.linux-mips.org/xcvs/linux-mips
>
> BTW, if you use this tool for tracking other trees, please drop me a
> note. Of course, I also like to have more developers to participate.
> Please join us at
>
> http://xcvs.sf.net
Very good!
I played with cvsps a few times, but didn't dare to use it
on such a large tree like the Linux kernel.
A few nits:
- I would prefer a "latest first" sort order in the patchset listing
- IMHO 'diff -up' would make the patchsets much easier to read
- could you please add a <title> tag for the query page? (For
easier bookmarking.)
The README from the sources mentions some constraints:
". Branching is always a complete branching of the whole tree."
What happens when only a part of a tree is branched?
". Commitment only modifies the head of a given branch."
I don't understand this. CVS commits will always change the head
of a branch (or the trunk) only, no?
How would one use xcvs on a repository with many different, but
interdependent CVS modules (e.g. gnome CVS http://cvs.gnome.org/)?
Johannes
next prev parent reply other threads:[~2004-02-05 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 23:08 [ANNOUNCE] "cvs explorer" for linux-mips CVS tree Jun Sun
2004-02-05 11:19 ` Geert Uytterhoeven
2004-02-05 18:05 ` Jun Sun
2004-02-05 18:15 ` Gleb O. Raiko
2004-02-05 19:39 ` Jun Sun
2004-02-05 20:22 ` Geert Uytterhoeven
2004-02-05 18:40 ` Johannes Stezenbach [this message]
2004-02-05 19:43 ` Jun Sun
2004-02-05 21:51 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040205184008.GC13068@convergence.de \
--to=js@convergence.de \
--cc=jsun@mvista.com \
--cc=linux-mips@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.