X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Message-ID: <49EA960D.9040808@users.sourceforge.net> Date: Sat, 18 Apr 2009 22:10:05 -0500 From: "Yaakov (Cygwin/X)" User-Agent: Thunderbird 2.0.0.21 (Windows/20090302) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: [ANNOUNCEMENT] [1.7] Updated: bash-completion-1.0-1 References: <49E90EAD DOT 5060206 AT users DOT sourceforge DOT net> <49E95082 DOT 3090509 AT byu DOT net> In-Reply-To: <49E95082.3090509@byu.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Eric Blake wrote: > Shipping it with cygport would probably be easiest, particularly since I > recently added the git-completion package which also installs into > /etc/bash_completion.d/. Another option would be submitting it for > upstream inclusion (the upstream development has really taken off lately, > with a lot of contributions being reviewed and added in their new git > repository). As cygport is Cygwin-specific, I think shipping it with cygport makes more sense. If I just grab the file from the previous release, will any changes be necessary for the current version? Yaakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEAREIAAYFAknqlg0ACgkQpiWmPGlmQSMwrwCeIhQJhWdZsL9VwxdwYOwC52zZ dhMAnAxKHzWIgQbqvOSBsXGKNOm9P7ab =M5g6 -----END PGP SIGNATURE----- -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/