From: "Davis Herring" <herring@lanl.gov>
To: "Noah Lavine" <noah549@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [patch] Tramp Scpc Autodetection
Date: Thu, 8 Apr 2010 12:35:37 -0700 (PDT) [thread overview]
Message-ID: <44934.130.55.118.19.1270755337.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <g2v16d22e431004080756p239954b3k9989aad1e9986161@mail.gmail.com>
> I'd like to do whatever is necessary to contribute this patch to
> emacs. What is necessary for that?
I'm not in charge, but you'll certainly need a copyright assignment for
this if you don't already have one: I believe you just need to write to
copyright-clerk@fsf.org and ask for the form, but if I'm wrong a
maintainer (Stefan or Chong) will correct me shortly.
After review/revision of the patch and your assignment (which usually
takes longer), someone will commit your patch quickly. Since this is a
user-visible change (if a minor one), a NEWS entry might be helpful.
> More generally, I couldn't find any information on the emacs website
> or in the manual about how to contribute to Emacs. Is this list the
> right place to send things like this?
Yes, although if you're reporting a bug (and possibly supplying a patch)
you should write to bug-gnu-emacs@gnu.org, which is backed by a database
so that bugs and patches don't get forgotten. For discussion of new
features or changes to the interface or so, this is the place; your case
is perhaps a gray area.
A few comments on the patch:
> +(defun detect-scpc ()
You should use the package prefix "tramp-" here.
> + (search-forward "OpenSSH_" nil t)
> + (looking-at "[0-9.]*")
> + (let ((ssl-version (read (match-string 0))))
> + (>= ssl-version 4.0))))))
This won't do the right thing if, say, the version is "4.3.2", because
`read' will treat it as a symbol, not a number. The obvious change is to
use "[0-9]+\\.?[0-9]*" as the regexp, which will also avoid an error if
there is no version string in the buffer at all (if, say, the process call
fails).
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
next prev parent reply other threads:[~2010-04-08 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 14:56 [patch] Tramp Scpc Autodetection Noah Lavine
2010-04-08 19:35 ` Davis Herring [this message]
2010-04-09 1:30 ` Glenn Morris
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=44934.130.55.118.19.1270755337.squirrel@webmail.lanl.gov \
--to=herring@lanl.gov \
--cc=emacs-devel@gnu.org \
--cc=noah549@gmail.com \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.