git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org,
	Carsten Mattner <carstenmattner@googlemail.com>,
	Jeff King <peff@peff.net>
Subject: Re: [PATCH 0/2] completion: backwards compatibility fix
Date: Sat, 19 May 2012 22:11:55 -0700	[thread overview]
Message-ID: <7vaa13bfms.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1337395295-29162-1-git-send-email-felipe.contreras@gmail.com> (Felipe Contreras's message of "Sat, 19 May 2012 04:41:33 +0200")

Felipe Contreras <felipe.contreras@gmail.com> writes:

> These two patches are meant to fix the backwards compatibility of _git, and
> _gitk.

Thanks.

Even though I think these two should be squashed into one "fix regression
that made _git and _gitk behave differently" commit (because otherwise the
result of applying the first one makes _git/_gitk disappear, shifting the
breakage from "older usage fails inside _git" to "older usage fails to
even find _git", the end result looks good.

  parent reply	other threads:[~2012-05-20  5:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-19  2:41 [PATCH 0/2] completion: backwards compatibility fix Felipe Contreras
2012-05-19  2:41 ` [PATCH 1/2] completion: rename _git and _gitk Felipe Contreras
2012-05-22  8:24   ` SZEDER Gábor
2012-05-22 18:00     ` Junio C Hamano
2012-05-22 18:52       ` Felipe Contreras
2012-05-19  2:41 ` [PATCH 2/2] completion: add support for backwards compatibility Felipe Contreras
2012-05-19  2:45 ` [PATCH 0/2] completion: backwards compatibility fix Jeff King
2012-05-19  7:54   ` Carsten Mattner
2012-05-19 15:31     ` Jeff King
2012-05-19 17:45       ` Carsten Mattner
2012-05-20  5:11 ` Junio C Hamano [this message]
2012-05-20  9:02 ` Carsten Mattner
2012-05-20 10:28   ` Felipe Contreras
2012-05-20 17:27     ` Carsten Mattner

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=7vaa13bfms.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=carstenmattner@googlemail.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).