From: Sverre Rabbelier <srabbelier@gmail.com>
To: John Tapsell <johnflux@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 4/6] Improve error message for git-filter-branch
Date: Thu, 19 Feb 2009 09:44:18 +0100 [thread overview]
Message-ID: <bd6139dc0902190044x623a9159p473278374df31c8d@mail.gmail.com> (raw)
In-Reply-To: <200902190736.35364.johnflux@gmail.com>
Heya,
On Thu, Feb 19, 2009 at 08:36, John Tapsell <johnflux@gmail.com> wrote:
> Tell the user that a backup (original) already exists, and how to solve
> this problem (with -f option)
Very helpful, I like it :)! Although perhaps s/Cannot backup/Cannot
create a new backup/ ?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-02-19 8:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 7:36 [PATCH 4/6] Improve error message for git-filter-branch John Tapsell
2009-02-19 8:44 ` Sverre Rabbelier [this message]
2009-02-19 14:19 ` John Tapsell
2009-02-19 15:03 ` Johannes Schindelin
2009-02-19 15:13 ` Sverre Rabbelier
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=bd6139dc0902190044x623a9159p473278374df31c8d@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=johnflux@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).