From: Peter Baumann <waste.manager@gmx.de>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: Starting 1.5.3 stabilization cycle
Date: Wed, 4 Jul 2007 00:16:28 +0200 [thread overview]
Message-ID: <20070703221628.GF4580@xp.machine.xx> (raw)
In-Reply-To: <Pine.LNX.4.64.0707031923180.4071@racer.site>
On Tue, Jul 03, 2007 at 07:27:54PM +0100, Johannes Schindelin wrote:
[... skipping an embarrassing part of the message :-) ...]
> > This is meant for reordering the commits, merge several commits into
> > one or even remove some of them.
>
> Or even better:
>
> - "git rebase" learned an "interactive" mode, where you can pick
> and reorder the commits to be applied.
Sounds nicer, but I would add that it is also possible to remove commits.
> > > - "git-filter-branch" is a reborn cg-admin-rewritehist.
> >
> > Better mention what it is for, e.g:
> >
> > Lets you rewrite GIT revision history by applying custom filters
> > on each revision. Those filters can modify each tree or
> > information about each commit.
>
> I never liked that description. How about (shameless plug) the description
> >from my last patch:
>
> git-filter-branch lets you rewrite the revision history of the
> current branch, creating a new branch. You can specify a number of
> filters to modify the commits, files and trees.
I find it a little distracting to mention the "new branch" in this short
description. I think this belongs into the manpage and not in a short
description for the release notes. But I agree that this sounds otherwise nicer.
-Peter
prev parent reply other threads:[~2007-07-03 22:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 7:29 Starting 1.5.3 stabilization cycle Junio C Hamano
2007-07-03 11:34 ` Frank Lichtenheld
2007-07-03 18:14 ` Peter Baumann
2007-07-03 18:27 ` Johannes Schindelin
2007-07-03 22:16 ` Peter Baumann [this message]
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=20070703221628.GF4580@xp.machine.xx \
--to=waste.manager@gmx.de \
--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 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.