From: Adam Spiers <git@adamspiers.org>
To: git list <git@vger.kernel.org>
Subject: Re: Re* [PATCH 2/2] check-ignore.c: fix segfault with '.' argument from repo root
Date: Wed, 20 Feb 2013 02:00:46 +0000 [thread overview]
Message-ID: <20130220020046.GC7860@pacific.linksys.moosehall> (raw)
In-Reply-To: <7v1ucc5b7n.fsf_-_@alter.siamese.dyndns.org>
On Tue, Feb 19, 2013 at 11:56:44AM -0800, Junio C Hamano wrote:
> Adam Spiers <git@adamspiers.org> writes:
>
> > Fair enough. I'll reply to this with a new version.[0]
> >
> > [0] I wish there was a clean way to include the new version inline,
> > but as I've noted before, there doesn't seem to be:
> >
> > http://article.gmane.org/gmane.comp.version-control.git/146110
>
> I find it easier to later find the patch if you made it a separate
> follow-up like you did, but you can do it this way if you really
> want to, using a scissors line, like so. Please do not try to be
> creative and change the shape of scissors just for the sake of
> chaning it.
[snipped]
OK, thanks for the information. IMHO it would be nice if 'git
format-patch' and 'git am' supported this style of inline patch
inclusion, but maybe there are good reasons to discourage it?
next prev parent reply other threads:[~2013-02-20 2:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 5:24 [BUG] git-check-ignore: Segmentation fault Zoltan Klinger
2013-02-19 13:40 ` Adam Spiers
2013-02-19 14:06 ` [PATCH 1/2] t0008: document test_expect_success_multi Adam Spiers
2013-02-19 14:06 ` [PATCH 2/2] check-ignore.c: fix segfault with '.' argument from repo root Adam Spiers
2013-02-19 17:54 ` Junio C Hamano
2013-02-19 19:07 ` Adam Spiers
2013-02-19 19:21 ` [PATCH v2 2/2] check-ignore.c, dir.c: " Adam Spiers
2013-02-19 19:59 ` Junio C Hamano
2013-02-19 22:03 ` Junio C Hamano
2013-02-20 1:57 ` Adam Spiers
2013-02-20 2:47 ` Junio C Hamano
2013-02-20 12:43 ` Adam Spiers
2013-02-20 1:30 ` Adam Spiers
2013-02-19 19:56 ` Re* [PATCH 2/2] check-ignore.c: " Junio C Hamano
2013-02-20 2:00 ` Adam Spiers [this message]
2013-02-20 2:53 ` Junio C Hamano
2013-02-20 10:47 ` Adam Spiers
2013-02-21 20:15 ` Junio C Hamano
2013-02-21 20:17 ` [PATCH 1/2] format-patch: rename "no_inline" field Junio C Hamano
2013-02-21 20:26 ` [PATCH 2/2] format-patch: --inline-single Junio C Hamano
2013-02-21 23:13 ` Jeff King
2013-02-21 23:41 ` Junio C Hamano
2013-02-21 23:47 ` Junio C Hamano
2013-02-22 15:32 ` Adam Spiers
2013-02-22 16:47 ` Junio C Hamano
2013-02-22 17:23 ` Jeff King
2013-02-19 17:37 ` [PATCH 1/2] t0008: document test_expect_success_multi 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=20130220020046.GC7860@pacific.linksys.moosehall \
--to=git@adamspiers.org \
--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).