public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.6.0-0.11
Date: Thu, 25 Aug 2016 15:29:00 -0000	[thread overview]
Message-ID: <b81a00a6-2a3f-1161-33f6-bd883f14298d@SystematicSw.ab.ca> (raw)
In-Reply-To: <20160825145212.GK9783@calimero.vinschen.de>

On 2016-08-25 08:52, Corinna Vinschen wrote:
> On Aug 25 08:38, Brian Inglis wrote:
>> On 2016-08-25 02:07, Corinna Vinschen wrote:
>>> You don't need mailx, btw.  After you created your patch with
>>> `git format-patch', you can send it with `git send-email' :)
>>
>> Looked for that, and everything there, but:
>>
>> $ uname -srvmo
>> CYGWIN_NT-10.0 2.5.2(0.297/5/3) 2016-06-23 14:29 x86_64 Cygwin
>> $ git --version
>> git version 2.8.3
>> $ man git | fgrep git-send-email
>>        git-send-email(1)
>> $ git help send-email
>> No manual entry for gitsend-email
>> $ git help git-send-email
>> No manual entry for git-send-email
>> $ man git-send-email
>> No manual entry for git-send-email
>> $ ls -1 /usr/share/man/man1/git* | wc -l
>> 143
>> $ ls /usr/share/man/man1/git-send-email*
>> ls: cannot access '/usr/share/man/man1/git-send-email*': No such file or directory
>> $ git send-email
>> git: 'send-email' is not a git command. See 'git --help'.
>
> Huh?  WJFFM:
>
> $ uname -a
> CYGWIN_NT-10.0 vmbert10 2.6.0(0.304/5/3) 2016-08-25 14:03 x86_64 Cygwin
> $ cygcheck -c git
> Cygwin Package Information
> Package              Version        Status
> git                  2.8.3-1        OK
> $ git --version
> git version 2.8.3
> $ ls -l /usr/share/man/man1/git-send-email*
> -rw-r--r-- 1 corinna vinschen 6835 May 24 18:55 /usr/share/man/man1/git-send-email.1.gz
> $ man git send-email
> GIT-SEND-EMAIL(1)                 Git Manual                 GIT-SEND-EMAIL(1)
> NAME
>        git-send-email - Send a collection of patches as emails
> SYNOPSIS
>        git send-email [options] <file|directory|rev-list options>...
>        git send-email --dump-aliases
> $ git send-email
> No patch files specified!
> git send-email [options] <file | directory | rev-list options >
> git send-email --dump-aliases

Eric pointed out that git-email is a separate package,
as I now find is git-completion, and others...
Hatess them, preciouss...

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2016-08-25 15:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-20 22:09 Corinna Vinschen
2016-08-23 13:41 ` Brian Inglis
2016-08-23 16:20   ` Corinna Vinschen
2016-08-24  8:22     ` Brian Inglis
2016-08-24  8:28       ` Brian Inglis
2016-08-24  8:31         ` Corinna Vinschen
2016-08-24 18:29           ` Brian Inglis
2016-08-24 18:53             ` Corinna Vinschen
2016-08-25  7:30               ` Brian Inglis
2016-08-25 10:03                 ` Corinna Vinschen
2016-08-25 14:46                   ` Brian Inglis
2016-08-25 14:48                     ` Eliot Moss
2016-08-25 15:01                     ` Corinna Vinschen
2016-08-25 15:29                       ` Brian Inglis [this message]
2016-08-25 22:23                       ` Eliot Moss
2016-08-25 15:21                     ` Eric Blake

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=b81a00a6-2a3f-1161-33f6-bd883f14298d@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).