From: Keith Packard <keithp@keithp•com>
To: Martin Langhoff <martin.langhoff@gmail•com>
Cc: keithp@keithp•com, Jim Radford <radford@blackbean•org>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: parsecvs tool now creates git repositories
Date: Fri, 07 Apr 2006 00:24:57 -0700 [thread overview]
Message-ID: <1144394697.2303.307.camel@neko.keithp.com> (raw)
In-Reply-To: <46a038f90604061622s5a7bee4eq6666d9b3796f70f6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 565 bytes --]
On Fri, 2006-04-07 at 11:22 +1200, Martin Langhoff wrote:
> parsecvs is committing them with the "added file foo.x" message, not
> the actual commit message.
heh. my cvs repositories are all so kludged that no files have ever been
added, it appears. I'll fix this when I've got a copy of the moodle
repository. sf.net is as useful as always.
I suspect the change is as simple as checking the format of the log
message and time time stamps of the commits and then just dropping the
1.1 revision from the tree entirely.
--
keith.packard@intel•com
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 191 bytes --]
next prev parent reply other threads:[~2006-04-07 7:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060405174247.GA29758@blackbean.org>
[not found] ` <1144262498.2303.231.camel@neko.keithp.com>
2006-04-06 6:36 ` Fixes to parsecvs Keith Packard
2006-04-06 12:08 ` Jan-Benedict Glaw
2006-04-06 14:48 ` Keith Packard
2006-04-06 15:26 ` Johannes Schindelin
2006-04-06 16:09 ` Jan-Benedict Glaw
2006-04-06 17:36 ` Keith Packard
2006-04-09 23:17 ` Francois Romieu
2006-04-06 18:15 ` parsecvs tool now creates git repositories Jim Radford
2006-04-06 20:12 ` Keith Packard
2006-04-06 21:51 ` Martin Langhoff
2006-04-06 22:19 ` Keith Packard
2006-04-06 23:22 ` Martin Langhoff
2006-04-07 7:24 ` Keith Packard [this message]
2006-04-02 5:36 Keith Packard
2006-04-02 9:39 ` Jan-Benedict Glaw
2006-04-02 19:31 ` Jan-Benedict Glaw
2006-04-03 4:10 ` Keith Packard
2006-04-03 4:38 ` Linus Torvalds
2006-04-03 7:25 ` Jan-Benedict Glaw
2006-04-03 13:58 ` Erik Mouw
2006-04-03 16:54 ` Keith Packard
2006-04-03 22:19 ` Keith Packard
2006-04-03 14:03 ` Erik Mouw
2006-04-03 14:21 ` Jakub Narebski
2006-04-03 14:39 ` Keith Packard
2006-04-03 14:37 ` Keith Packard
2006-04-03 15:32 ` Jeff King
2006-04-04 0:55 ` Anand Kumria
2006-04-03 22:38 ` Martin Langhoff
2006-04-04 2:07 ` Keith Packard
2006-04-04 2:16 ` Martin Langhoff
2006-04-04 2:24 ` Keith Packard
2006-04-04 2:42 ` Martin Langhoff
2006-04-04 3:51 ` Keith Packard
2006-04-04 6:09 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1144394697.2303.307.camel@neko.keithp.com \
--to=keithp@keithp$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=martin.langhoff@gmail$(echo .)com \
--cc=radford@blackbean$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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