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: Thu, 06 Apr 2006 15:19:28 -0700 [thread overview]
Message-ID: <1144361968.2303.288.camel@neko.keithp.com> (raw)
In-Reply-To: <46a038f90604061451m4522e3f3qceae2331751a307c@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Fri, 2006-04-07 at 09:51 +1200, Martin Langhoff wrote:
> - file additions were recorded with one-commit-per-file. I am not
> sure how rcs is recording these, but hte user does enter a common
> message at "commit" time. Perhaps the file addition action could be
> ignored then?
If the log message is identical, and the dates are in-range, parsecvs
"should" put the adds in the same commit.
> - some tags made on a branch show up in HEAD. This may be due to
> partial-tree branches, but I am not sure.
Finding branch points is not perfect; it's complicated by bizzarre
behaviour when adding files and casual CVS changes which make precise
branch points hard to detect. Can I get at this repository to play with?
I'd like to see if we can't get the branch point detection more
accurate.
--
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-06 22:27 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 [this message]
2006-04-06 23:22 ` Martin Langhoff
2006-04-07 7:24 ` Keith Packard
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=1144361968.2303.288.camel@neko.keithp.com \
--to=keithp@keithp.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=radford@blackbean.org \
/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.