Cvsweb not updating
At least some major committers who you will probably have to run your patch by heavily prefer context diffs.
Bizarrely, Git doesn't easily produce context diffs.
creates a new branch and checks it out at the same time.
Typically, you would develop each feature in a separate branch.
This addresses some of the key issues a sysadmin first runs into when they are designing or converting an infrastructure.
Bill Fenner is swamped and hasn't been able to do as much as he would like with CVSweb.
The pserver method can only be used for anonymous access.
The SSHv2 public key fingerprints for the machine hosting the cvs trees are: If you've never used CVS, you should read some documentation about it; a useful URL is
Most projects have a module with the same name of the project, where the main software development takes place. If your project already has an existing CVS repository that you want to move to Savannah, make an appointment with us for the migration.
So there is some need for fiddling around, either using the git://git.postgresql.org/git fetch super-fun-branch git checkout super-fun-branch #this will stage your remote branch for a local checkout git checkout -b super-fun-branch-name #the name can be wahtever you choose Now you have a local branch within your local git repo tracking a different branches history.
Most importantly, you can now push to that repo if you have to without making an explicit clone to track the history.
I've made some updates and added some more functionality in support of Hypersync; it's still a work in progress, but you can get my latest version of
You'll also need cgi-style.pl, though I'm thinking about removing the need for that (the Free BSD folks added the calls -- it's not a core part of cvsweb).
To subscribe to the Infrastructures mailing list, go to: Many folks know or have heard of the Linux Filesystem Standard (FSSTND), which specified what should go into /etc, /var, and so on.