All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Bernhard Reiter <ockham@raz.or.at>
Cc: git@vger.kernel.org
Subject: Re: Fwd: Re: [PATCH] git-imap-send: use libcurl for implementation
Date: Wed, 22 Oct 2014 10:47:27 -0700	[thread overview]
Message-ID: <xmqqbnp4hu8g.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <5447C7A8.7030502@raz.or.at> (Bernhard Reiter's message of "Wed, 22 Oct 2014 17:05:12 +0200")

Bernhard Reiter <ockham@raz.or.at> writes:

> *ping*
> Hope I didn't mess up formatting again...
> Or do I need to top-post, as the original thread is too old to keep posting to it?

Please avoid top-posting on this list.

If you have some background material (e.g. summary of previous
discussions, list of things that have been changed in response to
previous review, etc.), you have three options:

 * Use a cover letter, even for a one-patch topic.  Use [PATCH 0/1]
   for the background material if you have tons of it and then make
   [PATCH 1/1] as a follow-up to that cover letter.

   See http://thread.gmane.org/gmane.comp.version-control.git/256386
   for how such an approach looks like.

 * Use a single message, [PATCH] (aka [PATCH 1/1]), and add your
   background material _after_ three-dash lines as comment.

   See http://thread.gmane.org/gmane.comp.version-control.git/258451
   for how such an approach looks like.

 * Use a single message, [PATCH] (aka [PATCH 1/1]), and add your
   background material _before_ a scissors line "-- >8 --",
   optionally followed by "From:" and/or "Subject:" (but in your
   case, you are sending your own patch as yourself with the same
   subject, so neither of them apply).

   See http://thread.gmane.org/gmane.comp.version-control.git/258470/focus=258474
   for how such an approach looks like.


Thanks.

  reply	other threads:[~2014-10-22 17:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 22:40 [PATCH] git-imap-send: use libcurl for implementation Bernhard Reiter
2014-08-27 17:20 ` Junio C Hamano
2014-10-12 15:22   ` Bernhard Reiter
2014-10-22 15:05     ` Fwd: " Bernhard Reiter
2014-10-22 17:47       ` Junio C Hamano [this message]
2014-10-29 18:41   ` Bernhard Reiter
2014-10-29 20:56     ` Junio C Hamano
2014-11-09 13:00 ` Torsten Bögershausen
2014-11-09 14:55   ` Bernhard Reiter
2014-11-09 17:27     ` Ramsay Jones
2014-11-09 17:45       ` Junio C Hamano
2014-11-10 17:19     ` Junio C Hamano

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=xmqqbnp4hu8g.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ockham@raz.or.at \
    /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.