All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	git@vger.kernel.org
Subject: Re: [PATCH] Support of "make -s" in git-gui: do not output anything of the build itself
Date: Tue, 6 Mar 2007 19:14:10 -0500	[thread overview]
Message-ID: <20070307001410.GA26050@spearce.org> (raw)
In-Reply-To: <81b0412b0703061557j1cade6f6k4577da5e447a4e2a@mail.gmail.com>

Alex Riesen <raa.lkml@gmail.com> wrote:
> Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
> ---
> git-gui/Makefile |    5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)

Thanks.  It is applied to my git-gui tree.

BTW, Junio, I have taken your lead and defined a `maint` and a
`master` branch.  The `maint` branch of git-gui is meant to
corresponding in stability level to that of the `maint` branch
of git.git, meaning the one should always be suitable for direct
merging to the other.

If it is alright with Alex, I'd like to hold off on merging git-gui
into git.git right now.  We just got gitgui-0.6.3 merged, and I'd
like to see at least one version of git ship with a stable tag from
git-gui, rather than an arbitrary commit.  ;-)

-- 
Shawn.

  reply	other threads:[~2007-03-07  0:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 23:57 [PATCH] Support of "make -s" in git-gui: do not output anything of the build itself Alex Riesen
2007-03-07  0:14 ` Shawn O. Pearce [this message]
2007-03-07  0:48   ` [PATCH] make t8001 work on Mac OS X again Shawn O. Pearce
2007-03-07  1:00     ` Junio C Hamano
2007-03-07 18:07   ` [PATCH] Support of "make -s" in git-gui: do not output anything of the build itself 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=20070307001410.GA26050@spearce.org \
    --to=spearce@spearce.org \
    --cc=Johannes.Schindelin@gmx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.