From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Boyd Lynn Gerber <gerberb@zenez.com>
Cc: git@vger.kernel.org
Subject: Re: Patches for some OS's.
Date: Thu, 5 Jun 2008 19:37:17 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0806051935540.21190@racer> (raw)
In-Reply-To: <Pine.LNX.4.64.0806051114260.18454@xenau.zenez.com>
Hi,
On Thu, 5 Jun 2008, Boyd Lynn Gerber wrote:
> I have attached the patches necessary to use GIT on some Non Linux OS's.
One might think that you could now use Git to generate the patches, and
follow the conventions to submit them...
For example, reviewing attached patches makes it unduly hard on the
reviewers.
For example, you do not have any explanation AKA commit message.
For example, you use context diffs.
See Documentation/SubmittingPatches for more hints how to get your patches
integrated.
Hth,
Dscho
next prev parent reply other threads:[~2008-06-05 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 17:16 Patches for some OS's Boyd Lynn Gerber
2008-06-05 18:37 ` Johannes Schindelin [this message]
2008-06-05 18:49 ` Boyd Lynn Gerber
2008-06-05 19:07 ` Boyd Lynn Gerber
2008-06-05 19:35 ` Johannes Schindelin
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=alpine.DEB.1.00.0806051935540.21190@racer \
--to=johannes.schindelin@gmx.de \
--cc=gerberb@zenez.com \
--cc=git@vger.kernel.org \
/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