All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Litvinov <lan@ac-sw.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: cvsexportcommit/cvsimport workflow
Date: Mon, 21 Nov 2005 20:43:57 +0600	[thread overview]
Message-ID: <200511212043.57434.lan@ac-sw.com> (raw)

Hello,

Can ypu please explain how to use cvsimport with cvsexportcommit scripts ? 

I have tried these steps:
1. Make git repo from cvs repo using cvsimport command - everything works 
great.
2. Start traking cvs changes by incremental running cvsimport - It works.
3. Change files in git repo (master branch) - works :-)
4. Export git commits to cvs: 
      first question: What should be exported and in what order ? Lets skip 
this part - it is the smallest problem.
      Two test commits were exported to cvs without any problmes.
5. Importing cvs again - I have found my exported commits became separate 
commits in git repo in origin branch (solved by git-pull . origin). But thay 
were merged idealy.
6. Changing files again in git.
7. Export git commits to cvs: What should be exported question become harder 
and harder. Possible I should use some tag and run:
git-rev-list MY-TAG..master | xargs -n 1 git-cvsexportcommit -vX -cX (by the 
way, why just -v -c does not work ? I must add something to make options 
work)

This cycle is a bit of mess. I can write some scripts but I have no idea how 
this is supposed to work !

The biggest problem - conflict. I should resove them twice, during merging 
origin branch to master and when exporting these changes to cvs. By the way, 
I still can't export merge commit :-)

Thanks for help.
Alexander Litvinov.

             reply	other threads:[~2005-11-21 14:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-21 14:43 Alexander Litvinov [this message]
2005-12-05 20:57 ` cvsexportcommit/cvsimport workflow Martin Langhoff

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=200511212043.57434.lan@ac-sw.com \
    --to=lan@ac-sw.com \
    --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 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.