From: Tim Moore <timoore@redhat.com>
To: frysk <frysk@sourceware.org>
Subject: vendor branches in git repository
Date: Thu, 11 Oct 2007 12:00:00 -0000 [thread overview]
Message-ID: <470E105E.7000601@redhat.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I've pushed all the vendor branches I could identify to the sourceware .git repository
with the names vendor/LIBUNWIND, etc. Please let me know if anything is missing or
they don't resemble what you imported. The merge points of these branches back into the
main trunk didn't survive the cvs export process (or didn't exist in the first place) so
in Git these branches never appear to be merged back. I'm going to assert that it's not
necessary to massage the history to recreate the merges, as the commits to the mainline
that did the merges are certainly there, but if you disagree, let me know.
What other branches in CVS are important to preserve in the git repository?
I'm going to do a pass over the git repository to correct email names of contributors, so
don't get too attached to your clones of the current repo; the history will change out
from under you.
Tim
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFHDhBeeDhWHdXrDRURAr+EAJkBP/JwYKayJxtOKCWtDNQ5HU3jKwCeK2K5
1I8slI/L4C18AkdYkLMyBbY=
=xadx
-----END PGP SIGNATURE-----
next reply other threads:[~2007-10-11 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 12:00 Tim Moore [this message]
2007-10-12 14:19 ` Andrew Cagney
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=470E105E.7000601@redhat.com \
--to=timoore@redhat.com \
--cc=frysk@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).