bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: joseph at codesourcery dot com
Subject: [Bug binutils/14768] Checklist: Binutils Migration To Git
Date: Fri, 30 Aug 2013 23:47:38 +0000

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

--- Comment #17 from joseph at codesourcery dot com <joseph at codesourcery dot 
com> ---
On Fri, 30 Aug 2013, hp at sourceware dot org wrote:

> * Git migrations and work-flow offered for remaining projects
> (like newlib and cgen).

That should be in the form: document in detail how the migration worked, 
so that if the newlib community chooses to move to git, it has the benefit 
of documentation of the process when replicating it to move to its own git 
repository.

> * (related:) Do not set in stone this git repo as "binutils+gdb"
> in any documentation changes and names assuming we agree that other projects
> may be added.

Rather, I say the repository should be exactly 6(b) from 
<http://gcc.gnu.org/ml/gcc/2011-03/msg00486.html> (subject to confirming 
the exact set of directories with only Attic contents in CVS whose history 
gets converted).  (c), (d), (e), (f), (g) and each of the three parts of 
(h) should, if someone in their respective communities wishes to convert 
them away from CVS, be converted independently to separate repositories 
(based on shared toplevel code only when it's actually used); (a) may be 
convenient to avoid shared files diverging, but is not required.

(I do not definitively assert whether (c) newlib and (d) winsup should be 
separate or a single repository; that's for the relevant communities to 
work out.  I am confident that all the other divisions make sense.)

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



reply via email to

[Prev in Thread] Current Thread [Next in Thread]