git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "SZEDER Gábor" <szeder@ira.uka.de>
Cc: しらいしななこ <nanako3@bluebottle.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	git@vger.kernel.org
Subject: Re: [PATCH 1/2] git add: add long equivalents of '-u' and '-f' options
Date: Sun, 15 Jun 2008 13:21:57 -0700	[thread overview]
Message-ID: <7vlk16cuu2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080615085305.GA7003@neumann> (SZEDER Gábor's message of "Sun, 15 Jun 2008 10:53:05 +0200")

SZEDER Gábor <szeder@ira.uka.de> writes:

> On Sun, Jun 15, 2008 at 08:43:12AM +0900, しらいしななこ wrote:
>> Isn't this patch adding a new feature during the freezing period before
>> the release?  What is the policy of accepting such a patch in general?

The policy during the freeze is "bugfix only unless otherwise noted",
which is, admittedly, not saying much ;-)

> I think this patch is rather a bugfix in the user interface than a new
> feature.

Strictly speaking, this is a new feature but I think the documentation
value to clarify -u stands for "update" is great enough to make it an
exception.  I've rewritten (from empty!  Szeder, next time please write
sensible commit log message to defend your changes, instead of having _me_
to defend your changes to others here, like this) the commit log message
to clarify this point.

  reply	other threads:[~2008-06-15 20:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14  9:48 [PATCH 1/2] git add: add long equivalents of '-u' and '-f' options SZEDER Gábor
2008-06-14  9:48 ` [PATCH 2/2] bash: add more 'git add' options SZEDER Gábor
     [not found] ` <200806142344.m5ENiLqk020529@mi0.bluebottle.com>
2008-06-15  8:53   ` [PATCH 1/2] git add: add long equivalents of '-u' and '-f' options SZEDER Gábor
2008-06-15 20:21     ` Junio C Hamano [this message]
2008-06-15 21:23       ` SZEDER Gábor

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=7vlk16cuu2.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=nanako3@bluebottle.com \
    --cc=spearce@spearce.org \
    --cc=szeder@ira.uka.de \
    /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).