From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] diff --check: use colour
Date: Fri, 26 Jan 2007 18:41:19 +0100 [thread overview]
Message-ID: <epdedp$s0o$1@sea.gmane.org> (raw)
In-Reply-To: 200701261637.01199.andyparkins@gmail.com
Andy Parkins wrote:
> On Friday 2007 January 26 15:49, Bill Lear wrote:
>
>> I presume that I send the patch text to the list with the subject line
>> that starts with [PATCH], some sensible topic (e.g., "document --check
>> option to diff"), and then a short body of explanation and then,
>> following my signature, the patch itself.
>
> git-format-patch will make you an email of the correct form. Personally I do
> this (this is the IMAP server version, but it's similar for mbox)
You can use git-send-email to send emails via SMTP. I have configured
sendmail to send emails via gmail
-dnl define(`SMART_HOST',`smtp.your.provider')
+define(`SMART_HOST',`[smtp.gmail.com]')
> * make myself a branch from current master
> * write patch/patches, test (yeah, right ;-))
The same for me (with the exception that I branch from origin).
If writing patches takes longer time, and upstream has
advanced in meantime, I also rebase before sending patches.
* rebase branch using "git rebase master <branch>"
> * git-format-patch --stdout HEAD^ to check it looks good
> * git-format-patch --stdout HEAD^ | git-imap-send
> * Go to Drafts mailbox, open it up, add any additional comments for the
> mailing list only underneath the "---" and before the diffstat. Make sure
> you turn word wrap off as soon as you open the mail. Word wrapping will
> ruin the patch.
For me it is "git format-patch HEAD^.." if it is one patch (one commit)
only, "git format-patch -o mdir.<n> origin.." if this is series of patches.
Then edit the patches (the 0001-*.txt file), adding any additional
comments for the mailing list only underneath the "---" and before
the diffstat.
> * Send.
Use "git send-email <patch>" or "git send-email mdir.<n>" to send patches.
> * Wait for huge feeling of disappointment because your patch is junk and
> gets savaged by the git-gurus (maybe this step is just for me though).
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-01-26 17:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 14:05 [PATCH] diff --check: use colour Johannes Schindelin
2007-01-24 23:18 ` Junio C Hamano
2007-01-25 9:16 ` Johannes Schindelin
2007-01-25 22:23 ` Junio C Hamano
2007-01-25 22:49 ` Bill Lear
2007-01-25 23:41 ` Johannes Schindelin
2007-01-26 0:06 ` Bill Lear
2007-01-26 4:31 ` Jeff King
2007-01-26 11:10 ` Andreas Ericsson
2007-01-26 12:05 ` Andy Parkins
2007-01-26 13:52 ` Bill Lear
2007-01-26 15:49 ` Bill Lear
2007-01-26 16:00 ` J. Bruce Fields
2007-01-26 16:07 ` Bill Lear
2007-01-26 16:06 ` Bill Lear
2007-01-26 17:19 ` Jeff King
2007-01-26 17:26 ` Jakub Narebski
2007-01-26 16:37 ` Andy Parkins
2007-01-26 17:41 ` Jakub Narebski [this message]
2007-01-26 0:17 ` Junio C Hamano
2007-01-26 21:15 ` Johannes Schindelin
2007-02-18 0:25 ` Junio C Hamano
2007-02-18 0:47 ` Johannes Schindelin
2007-02-18 1:06 ` Junio C Hamano
2007-02-18 1:15 ` Johannes Schindelin
2007-02-18 16:27 ` [PATCH for "master"] " 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='epdedp$s0o$1@sea.gmane.org' \
--to=jnareb@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.