On Nov 16, 2007, at 10:24 PM, Stepan Kasal wrote:
[sending again, sorry if it arrives twice]Hi all, here is a doc correction which I have just made. OK to commit? If yes, how do I commit it? ;-)
If you have commit access to the autoconf repo, setup a remote for the git+ssh access:
git remote add sv ssh://git.sv.gnu.org/srv/git/autoconf.git then push your commits there: git push sv(you might want to see what gets pushed beforehand: git push -v --dry- run)
Or, change your `origin' branch so that it actually fetches from ssh://git.sv.gnu.org/srv/git/autoconf.git. Subsequent calls to git push (with no argument) will push stuff there by default.
If you don't have commit access, well, wait for someone to approve and push your commit :)
Have a nice day,
Stepan
* doc/autoconf.texi (Generic Programs): Do not say that the *_TOOL
macros canonicalize, they simply use the `host_alias'.
---
When sending patches with git-send-email, the comments that aren't part of the commit message must go here, after the 3 dashes. The reason behind this is that in order to import your commit in Git, people will save the raw email and use git-am email.raw which will scan the mail headers and then take the entire body of the mail up to `^---$' as the commit message. The comes the diffstat, which is ignored, and which is thus the place where comments irrelevant to the commit message should go (admittedly this is not natural at the beginning, but you get used to it).
doc/autoconf.texi | 7 +++---- 1 files changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/autoconf.texi b/doc/autoconf.texi index c7f8d2a..4cf0563 100644 --- a/doc/autoconf.texi +++ b/doc/autoconf.texi@@ -3950,10 +3950,9 @@ uses to produce objects, archives or executables}.@ovar{value-if-not-found}, @dvar{path, $PATH}) @acindex{CHECK_TOOL}Like @code{AC_CHECK_PROG}, but first looks for @var{prog-to-check- for}-with a prefix of the host type as determined by[EMAIL PROTECTED], followed by a dash (@pxref {Canonicalizing}).-For example, if the user runs @samp{configure --host=i386-gnu}, then -this call:+with a prefix of the host type as specified by @option{--host} , followed by a+dash. For example, if the user runs [EMAIL PROTECTED] --build=x86_64-gnu --host=i386-gnu}, then this call:
s/call/&s/
@example AC_CHECK_TOOL([RANLIB], [ranlib], [:]) @end example
Looks good to me. -- Benoit Sigoure aka Tsuna EPITA Research and Development Laboratory
PGP.sig
Description: This is a digitally signed message part
