From: Jim Meyering <jim@meyering.net>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
Tom Tromey <tromey@redhat.com>,
gdb-patches@sourceware.org
Subject: Re: gdb_7_3-branch not buildable?
Date: Tue, 03 May 2011 10:51:00 -0000 [thread overview]
Message-ID: <87iptsrrb0.fsf@rho.meyering.net> (raw)
In-Reply-To: <20110419150111.GA2601@adacore.com> (Joel Brobecker's message of "Tue, 19 Apr 2011 08:01:11 -0700")
Joel Brobecker wrote:
>> > Andreas, could you say what you did to make yours better?
>>
>> Handcraft. These are things that something based on cvsps cannot do
>> better.
>
> Can we take your branch and force-push it? If we could do that
> without confusing cvsps, that'd be awesome. git really has become
> a significant time saver, and not having a correct mirror of the
> branch would mean a lot of work on my end.
Hi Joel,
I've adjusted git's gdb_7_3-branch so that it is much closer to cvs now.
Diffs below.
For the record, I've done the following in a local, private clone.
# Rebase to proper branch point:
git tag gdb_7_3-2011-04-01-branchpoint c73dde705c3b163b5101ed4cc4506cef6cc58905
git branch --track v7.3 remotes/origin/gdb_7_3-branch && git co v7.3
git rebase --onto gdb_7_3-2011-04-01-branchpoint master v7.3
# Update the mirror repo used to sync from cvs:
git push ~/mirror-git-to-cvs/repo/src +v7.3:gdb_7_3-branch
git push ~/mirror-git-to-cvs/repo/src tag gdb_7_3-2011-04-01-branchpoint
In a few minutes the twice-hourly sync-from-cvs script
will run and push that result to the public git repository.
==============================================
With that, here is the result of comparing the latest checked-out/cloned
directories from cvs and git:
Only in gdb-cvs: contrib
diff -u -r -x.git -xCVS gdb/gdb/doc/stabs.texinfo gdb-cvs/gdb/doc/stabs.texinfo
--- gdb/gdb/doc/stabs.texinfo 2011-05-02 18:47:22.530555384 +0000
+++ gdb-cvs/gdb/doc/stabs.texinfo 2011-01-05 05:09:54.000000000 +0000
@@ -40,7 +40,7 @@
@page
@tex
\def\$#1${{#1}} % Kluge: collect RCS revision info without $...$
-\xdef\manvers{\$Revision$} % For use in headers, footers too
+\xdef\manvers{\$Revision: 2.130 $} % For use in headers, footers too
{\parskip=0pt
\hfill Cygnus Support\par
\hfill \manvers\par
diff -u -r -x.git -xCVS gdb/gdb/gdb.1 gdb-cvs/gdb/gdb.1
--- gdb/gdb/gdb.1 2011-05-02 18:47:22.581555645 +0000
+++ gdb-cvs/gdb/gdb.1 2011-01-05 05:09:51.000000000 +0000
@@ -1,6 +1,6 @@
.\" Copyright (C) 1991, 1999, 2010, 2011 Free Software Foundation, Inc.
.\" See section COPYING for conditions for redistribution
-.\" $Id$
+.\" $Id: gdb.1,v 1.4 1999/01/05 00:50:50 jsm Exp $
.TH gdb 1 "22may2002" "GNU Tools" "GNU Tools"
.SH NAME
gdb \- The GNU Debugger
Only in gdb-cvs/gdb/testsuite/gdb.ada: mi_catch_ex
Only in gdb: .gitignore
next prev parent reply other threads:[~2011-05-03 10:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-15 22:29 Jim Meyering
2011-04-16 7:44 ` Andreas Schwab
2011-04-17 1:38 ` Joel Brobecker
2011-04-18 16:56 ` Tom Tromey
2011-04-18 17:47 ` Andreas Schwab
2011-04-19 15:01 ` Joel Brobecker
2011-04-19 16:16 ` Andreas Schwab
2011-05-03 10:51 ` Jim Meyering [this message]
2011-05-03 13:10 ` Andreas Schwab
2011-05-03 13:32 ` Jim Meyering
2011-05-03 13:50 ` Andreas Schwab
2011-05-03 14:37 ` Jim Meyering
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iptsrrb0.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=schwab@linux-m68k.org \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox