From: Charles Bailey <charles@hashpling.org>
To: Andreas Ericsson <ae@op5.se>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 1/1] Make git archive respect core.autocrlf when creating ...
Date: Thu, 18 Sep 2008 21:29:29 +0100 [thread overview]
Message-ID: <20080918202929.GA9948@hashpling.org> (raw)
In-Reply-To: <48D2B831.8080206@op5.se>
On Thu, Sep 18, 2008 at 10:21:05PM +0200, Andreas Ericsson wrote:
> If it fixes the broken test while all the other tests still
> pass, I can only assume it's doing something right.
Only if you believe that I added a sensible test in the first place :-)
> The topic is a bit long though. Could you change it to
> "git archive: respect core.autocrlf when creating zip archives"
> so that it fits comfortably in one line when running "git log"
> on 80 char wide terminals?
Sorry, I made it <= 72 chars in my commit message and then forgot that
git format-patch adds the [PATCH] tag.
> As a side-note, you needn't put "1/1" in the [PATCH] section.
> That's usually done to make sure patches are applied in the
> right order when sending a series, but since a series of 1
> is kinda hard to jumble.. ;-)
I thought that the patch (a single commit) didn't really warrant a patch
series - being a one liner - but I made the test 0 of 1 so that people
could see the test failure first before deciding whether my proposed
patch was good or not. Sorry for the confusion.
Charles.
next prev parent reply other threads:[~2008-09-18 20:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1a7cc4db062b7df0dae0f27b29dba66c9d917e59.1221767629.git.charles@hashpling.org>
2008-09-18 20:01 ` [PATCH 1/1] Make git archive respect core.autocrlf when creating zip format archives Charles Bailey
2008-09-18 20:08 ` Charles Bailey
2008-09-18 20:21 ` Andreas Ericsson
2008-09-18 20:29 ` Charles Bailey [this message]
2008-09-18 20:53 ` [PATCH 1/1] Make git archive respect core.autocrlf when creating Sverre Rabbelier
2008-09-18 20:41 ` [PATCH 1/1] Make git archive respect core.autocrlf when creating zip format archives René Scharfe
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=20080918202929.GA9948@hashpling.org \
--to=charles@hashpling.org \
--cc=ae@op5.se \
--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 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.