From: "Shawn O. Pearce" <spearce@spearce.org>
To: Rogan Dawes <lists@dawes.za.net>
Cc: David Frech <david@nimblemachines.com>, git@vger.kernel.org
Subject: Re: [PATCH] Support wholesale directory renames in fast-import
Date: Tue, 10 Jul 2007 09:55:54 -0400 [thread overview]
Message-ID: <20070710135554.GK4436@spearce.org> (raw)
In-Reply-To: <469346D8.4080906@dawes.za.net>
Rogan Dawes <lists@dawes.za.net> wrote:
> Shawn O. Pearce wrote:
> >-Zero or more `filemodify`, `filedelete` and `filedeleteall` commands
> >+Zero or more `filemodify`, `filedelete`, `filename` and
> ^^ filerename
Ugh. Thanks. I just pushed out a corrected version.
--
Shawn.
prev parent reply other threads:[~2007-07-10 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 1:09 how to do directory renames in fast-import David Frech
2007-07-10 3:10 ` [PATCH] Support wholesale " Shawn O. Pearce
2007-07-10 4:16 ` David Frech
2007-07-10 14:03 ` Uwe Kleine-König
2007-07-10 14:14 ` Shawn O. Pearce
2007-07-10 19:55 ` David Frech
2007-07-11 7:57 ` Shawn O. Pearce
2007-07-11 23:11 ` David Frech
2007-07-10 8:44 ` Rogan Dawes
2007-07-10 13:55 ` Shawn O. Pearce [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=20070710135554.GK4436@spearce.org \
--to=spearce@spearce.org \
--cc=david@nimblemachines.com \
--cc=git@vger.kernel.org \
--cc=lists@dawes.za.net \
/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).