git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>, git@vger.kernel.org
Subject: Re: CVS to git: parsing ChangeLog entries?
Date: Fri, 14 Mar 2008 19:40:33 +0100	[thread overview]
Message-ID: <47DAC6A1.7070400@alum.mit.edu> (raw)
In-Reply-To: <20080312190827.GE3198@ins.uni-bonn.de>

I'll answer your questions from the point of view of cvs2git, a.k.a.
cvs2svn (http://cvs2svn.tigris.org).

Ralf Wildenhues wrote:
> when migrating a project that uses GNU-style ChangeLogs from CVS
> to git, is it possible to extract patch author information from
> the ChangeLog entries rather than from the CVS commit logs?
> For simplicity let's first assume the project used only one
> ChangeLog file.
> 
> Asking because it is not uncommon that patches are committed on
> behalf of other people, and it would be nice to credit them.

There is no builtin support for this in cvs2git.  But the place where
the author is determined knows about the whole changeset, including any
simultaneous changes to the changelog.  So it should be possible to add
this functionality without too much work.

> Related question: when CVS commit logs have varying encoding,
> say, some latin1 and some UTF-8, is it possible to have uniformly
> encoded git log entries?

cvs2git allows you to specify multiple encodings.  It tries one after
the other until one works successfully.  It also has hooks where you can
add your own decoder using arbitrary Python code.

That reminds me that there is a Python universal decoder that uses
heuristics to determine the encoding of an arbitrary octet stream.  That
might be a nice thing to add support for....

Michael

      parent reply	other threads:[~2008-03-14 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12 19:08 CVS to git: parsing ChangeLog entries? Ralf Wildenhues
2008-03-13 17:03 ` Jeff King
2008-03-15 10:38   ` Ralf Wildenhues
2008-03-14 18:40 ` Michael Haggerty [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=47DAC6A1.7070400@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=git@vger.kernel.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 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).