https://sourceware.org/bugzilla/show_bug.cgi?id=14768
Tom Tromey changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://sourceware.org/bugzilla/show_bug.cgi?id=14768
Tom Tromey changed:
What|Removed |Added
Assignee|fred.cooke+nospam at gmail dot com |tromey at redhat dot com
--- Comm
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #21 from Hans-Peter Nilsson ---
(In reply to Hans-Peter Nilsson from comment #16)
> * Add remaining "partial checkout" methods as mentioned in
> CVSROOT/modules to src-release, for related migrating projects (well, at
> least "sim")
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #20 from Hans-Peter Nilsson ---
(In reply to Tom Tromey from comment #19)
> (In reply to Hans-Peter Nilsson from comment #18)
>
> > Sorry, there was an ambiguity here. By "work-flow" I meant
> > "git-migration-unrelated usual work
https://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #19 from Tom Tromey ---
(In reply to Hans-Peter Nilsson from comment #18)
> Sorry, there was an ambiguity here. By "work-flow" I meant
> "git-migration-unrelated usual work-flow, of checking out and building and
> committing chan
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #18 from Hans-Peter Nilsson ---
(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
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #17 from 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 det
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
Hans-Peter Nilsson changed:
What|Removed |Added
CC||hp at sourceware dot org
--- Comm
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #15 from Tom Tromey ---
(In reply to Ian Lance Taylor from comment #13)
> My CVS stitching process is not so mysterious, it's in the CVS repository
> :ext:sourceware.org:/cvs/sourceware/coolo-cvs on the gccmerge branch. The
> main
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #14 from Tom Tromey ---
(In reply to Alan Modra from comment #11)
> Can I suggest a commit log policy change when we switch to git?
In my proposal I ask that these things be considered separately.
I'm in favor of many process chang
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #13 from Ian Lance Taylor ---
My CVS stitching process is not so mysterious, it's in the CVS repository
:ext:sourceware.org:/cvs/sourceware/coolo-cvs on the gccmerge branch. The main
command is in src/gccmerge.c. A few constants i
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #12 from Andreas Schwab ---
There should be an empty line after the subject line.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing li
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
Alan Modra changed:
What|Removed |Added
CC||amodra at gmail dot com
--- Comment #11 f
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #10 from Fred ---
OK, fair enough! As you were :-)
--
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https:/
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #9 from Tom Tromey ---
(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 calle
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #8 from Fred ---
Tom, I've been reading your updates to this, and enjoying seeing progress! :-)
About the last comment, though: Anything that disrupts current Git users should
probably be avoided. Get it into Git, sure, but why not
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #7 from Tom Tromey ---
Joseph pointed out that we want to stitch in the pre-sourceware
CVS history, which is available:
http://sourceware.org/ml/binutils/2012-10/msg00407.html
There are a few candidates for merging this in:
1. Wh
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #6 from Tom Tromey ---
I forgot a to-do item:
* Disable the current cvs->git importers
Also there is the question of what to call the resulting
repository. This affects at least the documentation.
I'm using "src.git" for now, but
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #5 from Tom Tromey ---
> * examine gdb and binutils documentation to see what needs to be
> updated. This means looking at the texinfo manuals, the web sites,
> and the gdb wiki.
I've done this locally.
--
You are receiving
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #4 from Tom Tromey ---
> * make src-release ignore .git (trivial)
> see the CVS_NAMES variable
Testing reveals that we don't need this.
> * update the gdbadmin scripts
I've done this but have not tested them.
> * port log_accu
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #3 from Tom Tromey ---
It would be helpful to collect a list of concrete tasks to be done.
I'm assuming, per the threads, that a shared gdb+binutils repository
would be created.
* make src-release ignore .git (trivial)
see the C
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
Ian Lance Taylor changed:
What|Removed |Added
CC||ian at airs dot com
--
Configure b
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
Tom Tromey changed:
What|Removed |Added
CC||tromey at redhat dot com
--
Configure bu
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #2 from Fred 2012-10-25
22:13:07 UTC ---
Thanks Joseph! Let's discuss this onthe list for maximum transparency and I'll
collate the results from past and present discussions here as we go! :-)
--
Configure bugmail: http://sourcew
http://sourceware.org/bugzilla/show_bug.cgi?id=14768
--- Comment #1 from joseph at codesourcery dot com 2012-10-25 22:06:51 UTC ---
My past messages to the various lists discuss the relevant issues. I
still think a combined binutils+gdb git repository (without any of the
other pieces from the
25 matches
Mail list logo
