All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>, "Hawkins\,
	Lisa M Mrs CTR USA USASOC-SOAR" 
	<lisa.hawkins1.ctr@soar.army.mil>
Subject: Re: rcs
Date: Wed, 06 Nov 2013 09:28:52 -0800	[thread overview]
Message-ID: <xmqqy5518mnf.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <5279071B.2070309@gmail.com> ("Jakub Narębski"'s message of "Tue, 05 Nov 2013 15:56:27 +0100")

Jakub Narębski <jnareb@gmail.com> writes:

> Finnerty, James M Mr CTR USA USASOC-SOAR wrote
>> Jeff King [mailto:peff@peff.net]wrote:
>>> On Tue, Oct 29, 2013 at 11:35:21AM -0500, Finnerty, James M Mr CTR USA USASOC-SOAR wrote:
>>>
>>>> Hi. I'm going to attempt to import a git database into Razor which is
>>>> linux rcs based. Does the linux version of git use rcs ?
>>>
>>> No, the formats are completely different, and you will have to translate.
>>> We don't usually get requests to go from git to rcs; it usually goes
>>> the other way. :)
>
>>
>>    Thanks.  We have several systems using Razor right now. So we are
>> trying to get all the systems into one CM system. Razor is just a gui
>> that uses rcs commands. Once we get everything synced we will explore
>> our options for a complete development CM system.
>
> The problem with using RCS as sync (as base) is that it is least
> powerfull of VCS, and as far as I know do not offer place to store
> extra information, so conversion from Git to RSS will lose some
> information (committership, signed commits and signed merges, signed
> tags, etc.).

You forgot to mention another important one: atomicity of commits
across the entire tree.  The best you could do would be to assume
that changes in such a collection of RCS ,v files from a Git export
to different files with the same timestamp and by the same author
are likely to have come from the same Git commit, and that the
timestamp monotonically increases, in order to stitch the history
back together.

      reply	other threads:[~2013-11-06 17:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-29 16:35 rcs Finnerty, James M Mr CTR USA USASOC-SOAR
2013-10-29 17:12 ` rcs Keshav Kini
2013-10-29 18:16 ` rcs Jeff King
2013-10-29 19:17   ` rcs Finnerty, James M Mr CTR USA USASOC-SOAR
2013-11-05 14:56     ` rcs Jakub Narębski
2013-11-06 17:28       ` Junio C Hamano [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=xmqqy5518mnf.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=lisa.hawkins1.ctr@soar.army.mil \
    --cc=peff@peff.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 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.