From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11603 invoked by alias); 22 Oct 2013 07:01:45 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 11580 invoked by uid 89); 22 Oct 2013 07:01:44 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS,T_FILL_THIS_FORM_SHORT autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 2 recipients X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 22 Oct 2013 07:01:43 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r9M71fg3013047 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 Oct 2013 03:01:41 -0400 Received: from barimba (ovpn-113-54.phx2.redhat.com [10.3.113.54]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r9M71eMl009981 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 22 Oct 2013 03:01:41 -0400 From: Tom Tromey To: GDB Development Subject: git is live CC: Binutils Development Date: Tue, 22 Oct 2013 07:01:00 -0000 Message-ID: <877gd5iyaz.fsf@fleche.redhat.com> MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2013-10/txt/msg00071.txt.bz2 Hi everybody. Git is now live and the master repository for binutils and gdb. Maybe I made some enormous mistake! While I'd prefer to be finished with this project, if there is a mistake, please be reassured that we have not taken any truly irreversible action. CVS commits are disabled, but all the data is still there. I hope you feel reassured now. Pedro pointed out today that the history of the existing repository is weird around the point at which the src repository is stitched onto the older devo repository. "Weird" here means that there are some commits that delete nearly everything, only to have it all restored a commit or two later. I spent some time trying to fix this; but in fact, far too much time, and in the end I decided that we will just have to live with it. It was pointed out to me on irc that not everybody has already used git. I'm reliably informed that this is a good git book, and it is available online: http://git-scm.com/book I'm sure there are others as well. A couple of small hints. You will want to set your username and email address in your git config before pushing your first commit. I'm sure the book explains this early on. I've set things up to reject "non-fast-forward" merge commits to master. What this means is that if you commit something and try to push, and then it fails, you will want to "git pull --rebase", or use "git rebase -i", before trying again. This is basically analogous to "cvs update"ing before trying to commit again. I named the new repository "binutils-gdb". First, sorry to all who backed "src". I was swayed by the hue and cry to choose a URL whose importance is undeniable despite the second argument to git clone. Second, gdbers, I chose the name alphabetically. The URLs: git://sourceware.org/git/binutils-gdb.git ssh://sourceware.org/git/binutils-gdb.git I believe only the latter form allows pushing. Please report any problems to me or to the list. I'll be around fixing any problems. You can also join us on #gdb and ask git questions if you like. I still have a few final tasks to do for the transition, but nothing too pressing. E.g., I will check in my changes to the gdbadmin scripts soon, when I'm readier to debug them; but meanwhile they will pull from CVS without harm. Tom