From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH] Add 'git fast-export', the sister of 'git fast-import'
Date: Wed, 28 Nov 2007 13:56:05 +0100 [thread overview]
Message-ID: <200711281356.06333.jnareb@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0711281221090.27959@racer.site>
Johannes Schindelin wrote:
> On Wed, 28 Nov 2007, Jakub Narebski wrote:
>> Yes, I could reencode commit messages...
>
> Right.
>
>> P.S. One nice use of proposed (at one time) 'note' header would be to
>> save revision identifier from the version control system you import (CVS
>> revision number, Subversion sequential revision number, etc.).
>
> Why not put it into the commit message? It is not information that git
> uses, so it does not belong into the commit header IMO. (IIRC I made the
> same point already at the time 'note' was discussed.)
There are no problems if communication is only in one direction,
i.e. if it is only import to git repository. If communication is
two-directional, for example importing CVS repository into git
and using git-cvsserver, or using Subversion repository with the
help of git-svn, you would want commit messages preserved exactly.
This includes not adding information about original revision id
to commit message, and not recoding commit message to other encoding.
Just a thought...
--
Jakub Narebski
Poland
prev parent reply other threads:[~2007-11-28 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 21:37 [PATCH] Add 'git fast-export', the sister of 'git fast-import' Johannes Schindelin
2007-11-26 1:16 ` Junio C Hamano
2007-11-26 12:39 ` Johannes Schindelin
2007-11-26 17:55 ` Junio C Hamano
2007-11-27 12:14 ` Johannes Schindelin
2007-11-27 2:08 ` Shawn O. Pearce
2007-11-27 11:31 ` Johannes Schindelin
2007-11-27 23:40 ` Jakub Narebski
2007-11-28 12:22 ` Johannes Schindelin
2007-11-28 12:56 ` Jakub Narebski [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=200711281356.06333.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).