git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: skimo@liacs.nl, git@vger.kernel.org
Subject: Re: Draft release notes for v1.5.3, as of -rc1
Date: Mon, 16 Jul 2007 00:53:58 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707160053130.14781@racer.site> (raw)
In-Reply-To: <7vvecmj1ju.fsf@assigned-by-dhcp.cox.net>

Hi,

On Sat, 14 Jul 2007, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > It is really unfortunate that rewrite-commits came in so late in the 
> > release cycle, and I am quite sure it should not be in 1.5.3.  There is 
> > just too much new in it, and too many things to flesh out.
> >
> > Junio, if you want to include it in 1.5.3, it should be marked as alpha 
> > code, as it has not seen any time in "next", let alone "master".
> 
> I am not considering rewrite-commits for inclusion right now.

Fair enough.

> I was hoping that filter-branch will stay.  Its interface is something 
> people are already familiar with since the days of its its older 
> incarnation cg-admin-rewritehist, and it would be really really nice 
> that anything that attempts to replace it builds on and extends its 
> external interface.
> 
> Maybe rewrite-commits can be used to delegate the implementation of 
> heavy lifting from filter-branch?  IOW can the latter be just a thin 
> wrapper around the former?

That is a very good idea.

Ciao,
Dscho

  reply	other threads:[~2007-07-15 23:54 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-13 22:30 What's in git.git (stable) Junio C Hamano
2007-05-17  0:21 ` Junio C Hamano
2007-05-19  5:24   ` Junio C Hamano
2007-05-23 21:46     ` Junio C Hamano
2007-05-29 10:12       ` Junio C Hamano
2007-06-02 21:09         ` Junio C Hamano
2007-06-07  2:08           ` Junio C Hamano
2007-06-13 20:11             ` Junio C Hamano
2007-06-13 22:31               ` Johannes Schindelin
2007-06-14  7:12                 ` Johannes Sixt
2007-06-21  7:21               ` Junio C Hamano
2007-06-25  9:43                 ` Junio C Hamano
2007-07-02  0:16                   ` Junio C Hamano
2007-07-13  6:06                     ` What's in git.git Junio C Hamano
2007-07-13  6:40                       ` Draft release notes for v1.5.3, as of -rc1 Junio C Hamano
2007-07-13  9:29                         ` Sven Verdoolaege
2007-07-14 14:22                           ` Johannes Schindelin
2007-07-14 18:13                             ` Junio C Hamano
2007-07-15 23:53                               ` Johannes Schindelin [this message]
2007-07-13 13:50                         ` Brian Downing
2007-07-13 15:31                           ` Junio C Hamano
2007-07-28  8:47                       ` What's in git.git (stable) Junio C Hamano
2007-07-28  8:56                         ` David Kastrup
2007-07-28  9:02                           ` Junio C Hamano
2007-07-28  9:35                           ` David Kastrup
2007-07-29  3:16                             ` Theodore Tso
2007-07-29  9:05                               ` David Kastrup
2007-07-29 16:40                                 ` Theodore Tso
2007-07-29 11:27                               ` Johannes Schindelin
2007-07-29 13:51                                 ` [Untested! proposal] git-mergetool.sh: introduce ediff option David Kastrup
2007-07-29 20:52                                   ` Theodore Tso
2007-07-29 23:30                                     ` David Kastrup
2007-07-28 12:28                         ` What's in git.git (stable) Thomas Glanzmann
2007-08-07  6:22                         ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0707160053130.14781@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=skimo@liacs.nl \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).