[Bug binutils/14768] Checklist: Binutils Migration To Git

[tromey at redhat dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=14768

--- Comment #9 from Tom Tromey <tromey at redhat dot com> ---
(In reply to Fred from comment #8)

> About the last comment, though: Anything that disrupts current Git users
> should probably be avoided. Get it into Git, sure, but why not just leave it
> on a branch called pre-sourceware or similar?

We're making a new gdb+binutils repository, for reasons outlined in the
various threads -- so current users will already be inconvenienced.

Note that the inconvenience is pretty small.  An existing branch can
be migrated quite easily via git am, just by finding the corresponding
branch point.  There are probably other ways as well.

> This should have been done up
> front really.

The history wasn't publicly available when the mirror was created.

> If it's being done now, everyone should be notified heavily
> before the existing history is smashed/re-hashed and anyone down stream is
> broken by it.

We won't overwrite gdb.git or binutils.git.  We'll have a new src.git
and mirroring to the existing it repositories will be disabled.
Current users will pay a small one-time transition cost.

-- 
You are receiving this mail because:
You are on the CC list for the bug.