trunk changes.
> > On that branch, use something like »git diff :/refs/top-bases/baseline«
> > to diff your working tree against the branch's base. When reviewing the
> > commit history on that branch, it may be helpful to exclude any bulk
> > merges from trunk, so u
mit history on that branch, it may be helpful to exclude any bulk
> merges from trunk, so use something like »git log HEAD ^origin/trunk«.
>
> Fotis and Svante, please base any futher work for the Hurd port for GCC
> Go on that branch. Send patches by email, for now.
>
> > I g
»git diff :/refs/top-bases/baseline«
to diff your working tree against the branch's base. When reviewing the
commit history on that branch, it may be helpful to exclude any bulk
merges from trunk, so use something like »git log HEAD ^origin/trunk«.
Fotis and Svante, please base any futher wo
Hi!
On Wed, 12 Jun 2013 15:36:39 +0200, Svante Signell
wrote:
> On Tue, 2013-06-11 at 10:31 +0200, Thomas Schwinge wrote:
> > On Fri, 07 Jun 2013 11:14:31 +0200, Svante Signell
> > wrote:
> > > Attached are patches to enable gccgo to build properly on Debian
> > > GNU/Hurd on gcc-4.7 (4.7.3-4)
Hi Thomas,
On Tue, 2013-06-11 at 10:31 +0200, Thomas Schwinge wrote:
> Hi!
>
> On Fri, 07 Jun 2013 11:14:31 +0200, Svante Signell
> wrote:
> > Attached are patches to enable gccgo to build properly on Debian
> > GNU/Hurd on gcc-4.7 (4.7.3-4).
>
> Thanks! I've begun integrating them into my GC
Hi!
On Fri, 07 Jun 2013 11:14:31 +0200, Svante Signell
wrote:
> Attached are patches to enable gccgo to build properly on Debian
> GNU/Hurd on gcc-4.7 (4.7.3-4).
Thanks! I've begun integrating them into my GCC tree (based on upstream
GCC trunk, so some changes to be done to your patches), and
