From: Andreas Schwab <schwab@suse.de>
To: David Kastrup <dak@gnu.org>
Cc: jim@meyering.net, emacs-devel@gnu.org
Subject: Re: Info about available CVS/Arch/Git branches
Date: Mon, 13 Aug 2007 16:32:25 +0200 [thread overview]
Message-ID: <je1we7ijye.fsf@sykes.suse.de> (raw)
In-Reply-To: <86r6m7kbyn.fsf@lola.quinscape.zz> (David Kastrup's message of "Mon\, 13 Aug 2007 11\:42\:08 +0200")
David Kastrup <dak@gnu.org> writes:
> It would appear that this repo is made from CVS. If it is feasible,
> it might me nicer to do this from the arch repo since that would
> presumably keep track of the merges (information that is missing from
> CVS). I've had mediocre success using git archimport however.
The arch repo is missing too much information to be useful for import.
> Maybe it is also possible to extract just the merge info (which commit
> was merged into which branch) in textual form from arch?
You can use the commit message to detect merges, but you'll have to hack
the import script to map the arch names back to the CVS branch names.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2007-08-13 14:32 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 15:59 Info about available CVS/Arch/Git branches Stefan Monnier
2007-08-09 20:57 ` Reiner Steib
2007-08-12 3:45 ` Michael Olson
2007-08-12 9:10 ` Andreas Schwab
2007-08-13 9:42 ` David Kastrup
2007-08-13 10:06 ` Jim Meyering
2007-08-13 10:21 ` David Kastrup
2007-08-13 10:52 ` dhruva
2007-08-13 11:05 ` David Kastrup
2007-08-18 9:20 ` Andreas Schwab
2007-08-18 10:39 ` dhruva
2007-08-20 4:22 ` Miles Bader
2007-08-20 6:12 ` dhruva
2007-08-13 11:50 ` Jim Meyering
2007-08-13 13:05 ` Andreas Schwab
2007-08-13 13:07 ` Jim Meyering
2007-08-13 13:28 ` Randal L. Schwartz
2007-08-13 14:46 ` Jim Meyering
2007-08-13 16:41 ` Jim Meyering
2007-08-13 14:32 ` Andreas Schwab [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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=je1we7ijye.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).