http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #18 from Hans-Peter Nilsson <hp at sourceware dot org> --- (In reply to jos...@codesourcery.com from comment #17) > On Fri, 30 Aug 2013, hp at sourceware dot org wrote: > > > * Git migrations and work-flow offered for remaining projects > > (like newlib and cgen). Sorry, there was an ambiguity here. By "work-flow" I meant "git-migration-unrelated usual work-flow, of checking out and building and committing changes to files affected by the migration changes", not specifically "work-flow of git migration" - though that makes sense too on its own. > 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. Not sure if your reply was affected by the ambiguity of my suggestion, but anyway your suggestion makes sense. > > * (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> If the src CVS is to be able to continue on its own then there's one or two missing TODO items last: * Undo the read-only marking of the subset of converted directories that are shared with non-migrated projects. (For example: config/) and * Alert all non-migrated projects affected by converted directories. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ bug-binutils mailing list bug-binutils@gnu.org https://lists.gnu.org/mailman/listinfo/bug-binutils
