Re: vendor branches in git repository

[Andrew Cagney <cagney@redhat.com>]

Tim Moore wrote:
> -----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.
>
>   
Right, re-discovering the merge points is pretty much impossible;  but 
we've hopefully dropped sufficient tags to find them.  vendor/BLAH 
sounds good!

Andrew




> 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-----
>