public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
Cc: cygwin@cygwin.com
Subject: Re: getpriority() and top display for priority is inconsistent
Date: Wed, 07 Aug 2019 08:08:00 -0000	[thread overview]
Message-ID: <20190807080821.GX11632@calimero.vinschen.de> (raw)
In-Reply-To: <BL0PR0901MB43081A3B1F1F397036D6958DA5D40@BL0PR0901MB4308.namprd09.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]

On Aug  7 00:45, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
> > You seem to have worked it out already so please send a patch in
> > git format-patch foramt to the cygwin-patches mailing list.
> 
> I tried :-/
> 
> <cygwin-patches@cygwin.com>:
> Sorry, only subscribers may post. (#5.7.2)

There are no subscribtion restrictions, you can simply subscribe.

> I do not use git to pull Cygwin sources.  The last snapshot (that
> corresponds to the last-known-stable release I'm allowed to use) is a
> little old, but here goes the diff patch:

This is much better with git, because of the commit message and
the fact that the diff is in the right format (-up).  You can send
the git format-patch output to this list if you don't want to 
subscribe to the (very low traffic) cygwin-patches ML.  Please give
it a try.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-08-07  8:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-07  0:45 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-07  8:08 ` Corinna Vinschen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-08-07 19:28 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-08  8:00 ` Corinna Vinschen
2019-08-06 18:54 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-06 20:08 ` Corinna Vinschen

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=20190807080821.GX11632@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    --cc=lavr@ncbi.nlm.nih.gov \
    /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).