() Bruno Haible <[EMAIL PROTECTED]>
() Thu, 6 Mar 2008 15:01:18 +0100
Thanks, I've applied a slightly different one. (I don't often
read about "registering with the VCS". "check in" is the more
common term. Also, when you say "marked as ignorable (for
example, by adding them to @file{.cvsignore}" - are there other
ways to mark a file as ignorable?).
It does seem that "check in" is used a lot. The only other data
point i have in mind is that Emacs, to support many VCSes, uses
the term "register". The idea is that "check in" implies "check
out", and the latter is confusing. Probably a little more verbose
but more explicit would be "put under control of". Whatever...
As for ignorability, i know that Git has .gitignore, plus a "user
ignore file" (which i recently learned about). For example:
$ cd
$ echo '*.o' > .git-global-ignore
$ git config core.excludesfile ~/.git-global-ignore
This makes Git ignore *.o for all my Git-managed projects.
Perhaps other VCSes sport other methods.
It was OK. For documentation patches, unified diffs (like those
that you sent) are generally preferred over context diff.
So i take it context diff is preferred for code patches?
2008-03-06 Bruno Haible <[EMAIL PROTECTED]>
Thanks for the quick update.
thi
