From: Junio C Hamano <gitster@pobox•com>
To: "Shawn O. Pearce" <spearce@spearce•org>
Cc: Brandon Casey <casey@nrlssc•navy.mil>,
git@vger•kernel.org, Arjen Laarhoven <arjen@yaph•org>,
Jeff King <peff@peff•net>, Mike Ralphson <mike@abacus•co.uk>
Subject: Re: What's in git.git (Oct 2008, #03; Tue, 14)
Date: Wed, 15 Oct 2008 13:26:03 -0700 [thread overview]
Message-ID: <7vhc7dr4f8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081015202032.GD28802@spearce.org> (Shawn O. Pearce's message of "Wed, 15 Oct 2008 13:20:32 -0700")
"Shawn O. Pearce" <spearce@spearce•org> writes:
>> If we can add a test case to demonstrate the existing breakage, I think we
>> can (and should) cherry-pick it to 'maint'.
>
> Yes, it probably should have gone to maint. No, it didn't go there.
> Temporary lapse in maintainer judgement.
That is Ok. I do the same all the time (and I try to rewind and rebuild
when I spot it before pushing the results out, but I am not always
successful).
I just wanted to see if there was any particular reason not to have this
on 'maint'.
Thanks.
next prev parent reply other threads:[~2008-10-15 20:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-14 22:08 What's in git.git (Oct 2008, #03; Tue, 14) Junio C Hamano
2008-10-15 15:35 ` Brandon Casey
2008-10-15 17:25 ` Mike Ralphson
2008-10-15 19:38 ` Junio C Hamano
2008-10-15 20:20 ` Shawn O. Pearce
2008-10-15 20:26 ` Junio C Hamano [this message]
2008-10-15 20:36 ` Shawn O. Pearce
2008-10-16 0:58 ` [PATCH maint 1/2] t4018-diff-funcname: rework negated last expression test drafnel
[not found] ` <1224118730-24711-1-git-send-email-drafnel@gmail.com>
2008-10-16 0:58 ` [PATCH maint 2/2] t4018-diff-funcname: demonstrate end of line funcname matching flaw drafnel
2008-10-16 10:08 ` What's in git.git (Oct 2008, #03; Tue, 14) Jeff King
2008-10-16 15:21 ` Brandon Casey
2008-10-16 15:37 ` Pieter de Bie
2008-10-17 7:02 ` Arjen Laarhoven
2008-10-24 2:44 ` Junio C Hamano
2008-10-17 9:53 ` Jeff King
2008-10-17 23:58 ` 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=7vhc7dr4f8.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=arjen@yaph$(echo .)org \
--cc=casey@nrlssc$(echo .)navy.mil \
--cc=git@vger$(echo .)kernel.org \
--cc=mike@abacus$(echo .)co.uk \
--cc=peff@peff$(echo .)net \
--cc=spearce@spearce$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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