From: Jim Meyering <jim@meyering.net>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Tom Tromey <tromey@redhat.com>,
GDB <gdb@sourceware.org>
Subject: Re: gdb.git mirror is broken
Date: Tue, 06 Oct 2009 14:33:00 -0000 [thread overview]
Message-ID: <87d4504mnl.fsf@meyering.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0910061415170.15615@digraph.polyomino.org.uk> (Joseph S. Myers's message of "Tue, 6 Oct 2009 14:26:23 +0000 (UTC)")
Joseph S. Myers wrote:
> On Tue, 6 Oct 2009, Jim Meyering wrote:
>
>> perhaps we should think ahead to the day if/when everyone
>> is using git and not CVS.
>
> The day when each project can choose its version control system, and
> change between systems, independently and without needing to change in
> sync with other projects, sounds much better to me. That there is any
> link at all between the development of GDB and Cygwin, for example, is a
> defect in the present system that should be fixed by the move of either
> project to another system.
>
>> If I need to make a change in gnulib, I don't change
>> coreutils/gnulib/, but rather make the change in a separate
>
> First and foremost, as I said in
> <http://sourceware.org/ml/binutils/2009-05/msg00117.html>, version control
> should make common tasks easy. That means a single command in a binutils
> checkout to commit both a BFD change and the testcases in the ld
> testsuite, for example. What things look like underneath is less
> important, and the exact spelling of the command is less important - but
> if it doesn't look like a single repository for common use cases like
> that, something is seriously wrong.
>
> Version control should also make mistakes hard - it should be hard to
> check in an incomplete patch by accident, or think you have checked in a
> change when it has not gone where it should, for example, and extremely
> hard to break the repository.
>
> (Advocates of any change also still need to work out the detailed designs,
> as I noted in <http://sourceware.org/ml/binutils/2009-05/msg00213.html>.)
No pressure from me.
I barely have time to help with the technical side of things,
so if you want someone willing to invest in advocacy I'm not your man.
next prev parent reply other threads:[~2009-10-06 14:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 0:31 H.J. Lu
2009-10-06 6:23 ` Pierre Muller
2009-10-06 6:45 ` Jim Meyering
2009-10-06 6:51 ` Jim Meyering
2009-10-06 7:38 ` Jim Meyering
2009-10-06 13:08 ` H.J. Lu
2009-10-06 14:07 ` Jim Meyering
2009-10-06 14:26 ` Joseph S. Myers
2009-10-06 14:33 ` Jim Meyering [this message]
2009-10-06 16:11 ` Joseph S. Myers
2009-10-07 4:29 ` Matt Rice
2009-10-10 5:35 ` Matt Rice
2009-10-06 16:06 ` Tom Tromey
2009-10-06 16:21 ` Jim Meyering
2009-10-06 15:45 ` Joel Brobecker
2009-10-06 18:38 ` Eli Zaretskii
2009-10-06 19:01 ` Joel Brobecker
2009-10-06 20:36 ` Eli Zaretskii
2009-10-06 21:10 ` Joel Brobecker
2009-10-06 22:04 ` Tom Tromey
2009-10-07 7:29 ` Eli Zaretskii
2009-10-07 7:27 ` Eli Zaretskii
2009-10-06 16:08 ` Tom Tromey
2009-10-06 16:09 ` 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=87d4504mnl.fsf@meyering.net \
--to=jim@meyering.net \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--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