git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Enable "git rerere" by the config variable rerere.enabled
Date: Sun, 8 Jul 2007 18:00:49 -0400	[thread overview]
Message-ID: <20070708220049.GD4436@spearce.org> (raw)
In-Reply-To: <7vejjkdaqe.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano <gitster@pobox.com> wrote:
> I'll exclude git-gui part and commit with a minor tweaks; having
> extra "does the directory exist" check in git-gui would not hurt
> people who are used to how rerere works in the short term, and I
> think I read somewhere that I should expect git-gui updates over
> the weekend anyway.

There is a slew of git-gui updates already made but not yet pulled
in by you, and a pile yet still coming.

I'm going to be hacking on git-gui pretty much the rest of today,
and probably a good deal tomorrow too.  I'm trying to simplify
the workflow for users in my 400+ branch production repository.
They are actively using git-gui now and really need the tool to
handle things for them.  Especially since all but 1 of the users
is _not_ command-line friendly.

So you can feel free to pull maint and master over if you want,
but you might just want to wait another day or two.

Are you thinking of doing a git 1.5.2.4?  I'd like to get the bug
fixes accumulating in git-gui's maint into 1.5.2.4 as gitgui-0.7.5.
If you are doing a 1.5.2.4 release that is...

-- 
Shawn.

  parent reply	other threads:[~2007-07-08 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-06 12:05 [PATCH] Enable "git rerere" by the config variable rerere.enabled Johannes Schindelin
2007-07-07  5:49 ` Junio C Hamano
2007-07-07 12:41   ` Johannes Schindelin
2007-07-08 22:00   ` Shawn O. Pearce [this message]
2007-07-08 21:36 ` Shawn O. Pearce

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=20070708220049.GD4436@spearce.org \
    --to=spearce@spearce.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).