From: john doe <johndoe65534@mail.com>
To: cygwin@cygwin.com
Subject: Re: getpriority() and top display for priority inconsistent
Date: Thu, 15 Aug 2019 11:13:00 -0000 [thread overview]
Message-ID: <59ed5564-2f9a-b092-a26e-834cd7d9dbd9@mail.com> (raw)
In-Reply-To: <7835f9dc5a850a68503a216887a69d4a@smtp-cloud7.xs4all.net>
On 8/15/2019 1:04 PM, Houder wrote:
> On Thu, 15 Aug 2019 12:20:38, Corinna Vinschen wrote:
>>
>> On Aug 15 09:41, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
>>>> git format-patch output with commit message, please?
>>> =20
>>> Please educate me how to do that; I am just using "git diff --no-color".
>>
>> $ git add <files with changes you want to commit>
>> $ git commit
>>
>> - opens editor to create a commit message. first line is summary,
>> second line stays empty, descriptive text follows in line 3+.
>>
So, your commit message should have the form of:
"Subject line
Commit message"
A subject line is maximum 50 character long
A subject line starts in the imperative mode and does not end with any
punctuation marks.
The commit message is 72 character long.
--
John Doe
--
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
next prev parent reply other threads:[~2019-08-15 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 20:01 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-15 7:29 ` Corinna Vinschen
2019-08-15 9:41 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-15 10:20 ` Corinna Vinschen
2019-08-15 10:23 ` Corinna Vinschen
2019-08-15 11:04 ` Houder
2019-08-15 11:13 ` john doe [this message]
2019-08-15 10:54 ` john doe
-- strict thread matches above, loose matches on Subject: below --
2019-08-08 13:46 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-08-08 15:40 ` 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=59ed5564-2f9a-b092-a26e-834cd7d9dbd9@mail.com \
--to=johndoe65534@mail.com \
--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).