From: Peter Karlsson <peter@softwolves.pp.se>
To: git@vger.kernel.org
Subject: Recording merges after repo conversion
Date: Tue, 9 Oct 2007 08:09:36 +0100 (CET) [thread overview]
Message-ID: <Pine.LNX.4.64.0710090807060.26773@ds9.cixit.se> (raw)
Hi!
I have a couple of repositories converted from CVS to Git using
parsecvs. Some are just converted, some I've continued to develop after
the conversion (and cloned a couple of times).
Since parsecvs gave me all the CVS branches, I would like to record the
merge points in the Git history, if possible. I have commited merges
with comments like "merged <branchname>", so I can probably find them
quite easily, and I do have the imported CVS branches available. Can I
record the merge information so git knows about them?
Is it safe to do so on a repository that has already been cloned (i.e,
will a later push/pull work)?
--
\\// Peter - http://www.softwolves.pp.se/
next reply other threads:[~2007-10-09 7:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 7:09 Peter Karlsson [this message]
2007-10-09 7:19 ` Recording merges after repo conversion Benoit SIGOURE
2007-10-30 13:34 ` Peter Karlsson
2007-10-30 14:29 ` Lars Hjemli
2007-10-30 21:06 ` Peter Karlsson
2007-10-30 21:46 ` Lars Hjemli
2007-10-31 2:28 ` Johannes Schindelin
2007-10-31 9:50 ` Peter Karlsson
2007-10-31 11:01 ` Johannes Schindelin
2007-10-31 12:07 ` Peter Karlsson
2007-10-31 12:32 ` Johannes Schindelin
2007-10-31 12:43 ` Johan Herland
2007-10-31 13:43 ` Johannes Schindelin
2007-10-31 14:37 ` Johan Herland
2007-10-31 15:03 ` Johannes Schindelin
2007-10-31 15:21 ` Johan Herland
2007-10-31 15:57 ` Johannes Schindelin
2007-10-31 16:43 ` Linus Torvalds
2007-10-31 17:08 ` Johan Herland
2007-10-30 15:05 ` Johannes Schindelin
2007-10-31 12:17 ` Peter Karlsson
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=Pine.LNX.4.64.0710090807060.26773@ds9.cixit.se \
--to=peter@softwolves.pp.se \
--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).