[pnfs] sorting out pnfs cvs
J. Bruce Fields
bfields at fieldses.org
Tue Feb 27 18:29:31 EST 2007
On Tue, Feb 27, 2007 at 06:02:54PM -0500, J. Bruce Fields wrote:
> (This is just a symlink to the repository I had before in
> ~bfields/linux-pnfs.git.) In theory you should then be able to make
> changes, record them with
>
> git commit -a
By the way, a couple minor requests for the commit messages, just to get
in the habit of what the kernel people will want:
1. Please begin the commit message with a single short (less
than 50 character) line summarizing the change, followed by a
blank line and then a more thorough description. Tools that
turn commits into email, for example, use the first line on
the Subject: line and the rest of the commit in the body.
2. Probably obvious, but--don't include the diff in the commit
message. Hopefully git's improved history browsing should
make that unnecessary.
Of course the more difficult part of getting this into the kernel,
besides getting it all working, will be figuring out how to break the
changes into smaller steps. The goal is to give hope that an interested
reviewer could read what's been done, especially for common NFS code,
which we want to be careful not to break.
The code seems to be in a very early stage yet, but there's the worry
that if we wait too long then the job of splitting things up may become
really scary. I'm not sure where to start-- maybe it would be possible
to split the changes into a sessions-only piece and a pnfs piece that
builds on it?
Anyway, the git documentation at:
http://www.kernel.org/pub/software/scm/git/docs/cvs-migration.html
might be helpful. See also the tutorial it references.
There's also a longer user manual at:
http://www.kernel.org/pub/software/scm/git/docs/user-manual.html
in addition to the usual man pages. (Most of the manual and a lot of
the tutorial is my work, so I'm painfully aware of their shortcomings,
and appreciate any feedback....)
--b.
More information about the pNFS
mailing list