git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] make index-pâck able to complete thin packs
Date: Thu, 26 Oct 2006 09:25:54 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610260924520.12418@xanadu.home> (raw)
In-Reply-To: <ehq0md$i44$2@sea.gmane.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 620 bytes --]

On Thu, 26 Oct 2006, Jakub Narebski wrote:

> Junio C Hamano wrote:
> 
> > Karl Hasselström <kha@treskal.com> writes:
> > 
> >> On 2006-10-26 09:50:48 +0200, Jakub Narebski wrote:
> >>
> >>> That said, git-am should understand QP with coding in mail headers.
> >>
> >> I really hope it does, since I just patched StGIT to generate such
> >> headers. (Out of pure vanity -- I don't want my name mangled!)
> > 
> > Sorry for an earlier hiccup.
> 
> That said, I don't think that Nicolas Pitre wanted to have "index-pâck"
> in subject instead of "index-pack".

Indeed.  I don't know how that â ended up there.


Nicolas

  reply	other threads:[~2006-10-26 13:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-26  3:28 [PATCH 1/3] make index-pâck able to complete thin packs Nicolas Pitre
2006-10-26  7:19 ` Junio C Hamano
2006-10-26  7:50   ` Jakub Narebski
2006-10-26  9:19     ` Karl Hasselström
2006-10-26  9:33       ` Junio C Hamano
2006-10-26  9:38         ` Karl Hasselström
2006-10-26  9:56         ` Jakub Narebski
2006-10-26 13:25           ` Nicolas Pitre [this message]
2006-10-26 10:13       ` Catalin Marinas
2006-10-26 10:58         ` Karl Hasselström
2006-10-26 11:52           ` Catalin Marinas
2006-10-26 11:57           ` Catalin Marinas
2006-10-26 14:06             ` stg mail Karl Hasselström
2006-10-27 22:28 ` [PATCH 1/3] make index-pâck able to complete thin packs Junio C Hamano
2006-10-28  0:41   ` Nicolas Pitre

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=Pine.LNX.4.64.0610260924520.12418@xanadu.home \
    --to=nico@cam.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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 NNTP newsgroup(s).