git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@gmail.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Better mail handling in stgit
Date: Sun, 18 Sep 2005 09:19:51 +0100	[thread overview]
Message-ID: <1127031591.6959.3.camel@localhost.localdomain> (raw)
In-Reply-To: <432C1B71.4090105@drzeus.cx>

On Sat, 2005-09-17 at 15:34 +0200, Pierre Ossman wrote:
> Fix some issues with the mail function in StGIT:
> 
>  * Allow multiple To/Cc/Bcc command line options.
> 
>  * Better parsing of mail addresses.

Applied. Thanks.

On a side note, since people don't usually send patches against the
latest HEAD and git-apply fails, I implemented a --base option for
import which applies the patch on a given commit id and performs a
three-way merge with the current HEAD. It's much easier to fix the diff3
conflicts than modify the patch file to apply cleanly (with no fuzz).

-- 
Catalin

      reply	other threads:[~2005-09-18  8:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-17 13:34 [PATCH] Better mail handling in stgit Pierre Ossman
2005-09-18  8:19 ` Catalin Marinas [this message]

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=1127031591.6959.3.camel@localhost.localdomain \
    --to=catalin.marinas@gmail.com \
    --cc=drzeus-list@drzeus.cx \
    --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;
as well as URLs for NNTP newsgroup(s).