git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Alex Riesen <raa.lkml@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Convert t6022 to use git-merge instead of git-pull
Date: Sat, 28 Apr 2007 12:11:59 +0100	[thread overview]
Message-ID: <46332BFF.2050805@shadowen.org> (raw)
In-Reply-To: <7vzm4wupew.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:
> Is this really necessary?
> 
> I would rather want to leave some tests use "git merge" while
> some others use "git pull ." to catch breakage of either form.

If we are saying git pull . foo and git merge foo forms are the same
then perhaps that whole bunch of tests should be converted such that
they are in for cmd in "merge" "pull ." loop, so we test both always.

-apw

  parent reply	other threads:[~2007-04-28 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 20:07 [PATCH] Convert t6022 to use git-merge instead of git-pull Alex Riesen
2007-04-25 21:15 ` Junio C Hamano
2007-04-25 22:12   ` Alex Riesen
2007-04-28 11:11   ` Andy Whitcroft [this message]
2007-04-29  7:17     ` 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=46332BFF.2050805@shadowen.org \
    --to=apw@shadowen.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=raa.lkml@gmail.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 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).