git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (May 2009, #02; Sun, 17)
Date: Sun, 17 May 2009 20:27:20 +0200	[thread overview]
Message-ID: <200905172027.22374.jnareb@gmail.com> (raw)
In-Reply-To: <7v1vqnipc0.fsf@alter.siamese.dyndns.org>

On Sun, 17 May 2009, Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> * jn/gitweb-cleanup (Mon May 11 19:45:11 2009 +0200) 8 commits
>>>  + gitweb: Remove unused $hash_base parameter from
>>>    normalize_link_target
>>>  + gitweb: Simplify snapshot format detection logic in
>>>    evaluate_path_info
>>>  + gitweb: Use capturing parentheses only when you intend to capture
>>>  + gitweb: Replace wrongly added tabs with spaces
>>>  + gitweb: Use block form of map/grep in a few cases more
>>>  + gitweb: Always use three argument form of open
>>>  + gitweb: Always use three argument form of open
>>>  + gitweb: Do not use bareword filehandles
>>
>> Why "gitweb: Always use three argument form of open" is twice here?
> 
> Perhaps you sent in a malformed message and I did not notice nor hand
> munge it?  Let's see...
> 
>       Message-ID: <200905110329.40666.jnareb@gmail.com>
> 
> Yeah, that's it.

Ooops. I have put v2 of 'gitweb: Localize magic variable $/' as a reply
to a wrong post, and forgot to massage the email... still, shouldn't
git-am pick up "Subject:" from a body of email?

Well, it is in 'next' already, so resend wouldn't help...

I'm sorry about that...
-- 
Jakub Narebski
Poland

  reply	other threads:[~2009-05-17 18:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-17  8:05 What's cooking in git.git (May 2009, #02; Sun, 17) Junio C Hamano
2009-05-17  9:45 ` Jakub Narebski
2009-05-17 17:58   ` Junio C Hamano
2009-05-17 18:27     ` Jakub Narebski [this message]
2009-05-17 11:41 ` David Aguilar
2009-05-18 13:36 ` Johan Herland
2009-05-18 19:40   ` Markus Heidelberg
2009-05-18 21:55     ` Johan Herland
2009-05-19  0:35       ` [PATCH] git-submodule: add support for --merge Johan Herland
2009-05-19  1:33       ` What's cooking in git.git (May 2009, #02; Sun, 17) Junio C Hamano
2009-05-19  7:23         ` Johan Herland
2009-05-19  8:17           ` Johannes Schindelin
2009-05-19  8:45             ` Johan Herland
2009-05-19 11:53               ` Johannes Schindelin
2009-05-19 13:26                 ` git submodule update --merge (Was: What's cooking in git.git (May 2009, #02; Sun, 17)) Johan Herland
2009-05-25 11:59                   ` Johan Herland
2009-05-25 18:33                     ` git submodule update --merge Junio C Hamano
2009-05-25 18:57                       ` Johannes Schindelin
2009-05-25 19:04                         ` Avery Pennarun
2009-05-25 19:54                           ` Johannes Schindelin
2009-05-25 22:48                             ` Johan Herland
2009-05-25 22:10                       ` Johan Herland
2009-05-25 23:15                     ` git submodule update --merge (Was: What's cooking in git.git (May 2009, #02; Sun, 17)) Peter Hutterer

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=200905172027.22374.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).