From: ams@gnu.org (Alfred M. Szmidt)
To: pmuldoon@redhat.com
Cc: joseph@codesourcery.com, gdb@sourceware.org
Subject: Re: GIT and CVS
Date: Thu, 13 Oct 2011 21:43:00 -0000 [thread overview]
Message-ID: <E1RET3g-0007YR-Kr@fencepost.gnu.org> (raw)
In-Reply-To: <m3obxkmx2i.fsf@redhat.com> (message from Phil Muldoon on Thu, 13 Oct 2011 21:54:45 +0100)
>> So why are we still on CVS? I'm not a release manager, so I do not have
>
> Because the complications associated with having many projects in the same
> repository are a lot of work to disentangle, and it is a lot of work to do
> the conversion (including all the infrastructure scripts, user
> instructions etc.) for any one project.
>
> I think binutils+gdb is the right unit to aim for getting into a separate
> repository, as discussed in
> <http://gcc.gnu.org/ml/gcc/2011-03/msg00486.html>.
Ok, thanks for your response. Beyond the reason why they were in
the same repository for how many years, why do they still have to
be?
Joseph mentioned other reasons as well, it isn't just because they
have been in a single tree for many years. One other thing worth
mentioning is that unified source builds are immensly useful.
I hack on GDB, and I really don't hack on much else. This is not
to diminish other projects, I just don't hack on them. While other
modules represented by other projects are important, I am trying to
understand the reason why this is a blocker? Building GDB requires
a lot of dependencies outside of what is provided in the
repository.
GDB only requires a normal POSIX system to compile.
> ChangeLogs are very useful whatever the version control system;
> it's routine to import snapshots from one system into another and
> the ChangeLogs are readily available to see what source version
> you actually have there. ChangeLogs are convenient to grep and
> much less I/O intensive than git operations are (especially when
> your checkout is on NFS).
You can also fix ChangeLog entries after the fact, which is not
possible with git's commit messages.
I nearly decided to delete that line from the email as I did not
want to dilute the arguments. I wrote the ChangeLog parser for
Eclipse as I found ChangeLogs tiresome to write when history
basically replaced it. I must admit, even when I hack on emacs, it
is still a pain. I'll continue to do it, if people find it useful.
However, git log is very, highly configurable. The options are
very broad. And, as you can generate a git log from a local
repository, the NFS thing should not be too difficult to overcome?
Could you explain how `git log' replaces ChangeLog? It doesn't do much
more than what `cvs log' does, so you still need to write which
function/variable was modified, and git log doesn't do that as far as
I know (it only lists which files, and how many lines where
added/delete which isn't very useful).
next prev parent reply other threads:[~2011-10-13 21:43 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 19:37 Phil Muldoon
2011-10-13 20:21 ` Joseph S. Myers
2011-10-13 20:55 ` Phil Muldoon
2011-10-13 21:33 ` DJ Delorie
2011-10-13 21:44 ` Phil Muldoon
2011-10-13 21:43 ` Alfred M. Szmidt [this message]
2011-10-13 21:51 ` Jan Kratochvil
2011-10-13 22:08 ` Eli Zaretskii
2011-10-13 22:25 ` Jan Kratochvil
2011-10-13 22:41 ` Alfred M. Szmidt
2011-10-13 22:44 ` Alfred M. Szmidt
2011-10-14 10:31 ` Eli Zaretskii
2011-10-13 22:19 ` Alfred M. Szmidt
2011-10-13 22:45 ` Jan Kratochvil
2011-10-13 23:37 ` Alfred M. Szmidt
2011-10-14 5:56 ` Jan Kratochvil
2011-10-14 6:51 ` Alfred M. Szmidt
2011-10-13 23:03 ` Phil Muldoon
2011-10-13 23:51 ` Alfred M. Szmidt
2011-10-14 6:01 ` Jan Kratochvil
2011-10-14 6:52 ` Alfred M. Szmidt
2011-10-14 7:01 ` Jan Kratochvil
2011-10-14 7:13 ` Alfred M. Szmidt
2011-10-14 15:39 ` Joseph S. Myers
2011-10-14 15:49 ` Jan Kratochvil
2011-10-13 21:51 ` Joseph S. Myers
2011-10-13 21:59 ` Jan Kratochvil
2011-10-13 22:08 ` Joseph S. Myers
2011-10-13 22:17 ` Eli Zaretskii
2011-10-14 5:03 ` Joel Brobecker
2011-10-14 8:04 ` Eli Zaretskii
2011-10-13 23:14 ` Phil Muldoon
2011-10-13 23:56 ` Joseph S. Myers
2011-10-14 6:04 ` Jan Kratochvil
2011-10-13 21:58 ` Eli Zaretskii
2011-10-13 23:20 ` Phil Muldoon
2011-10-14 8:13 ` Eli Zaretskii
2011-10-14 10:23 ` Mark Kettenis
2011-10-14 10:55 ` Eli Zaretskii
2011-10-14 14:09 ` Li, Rongsheng
2011-10-14 12:54 ` Jan Kratochvil
2011-10-14 13:07 ` Jonas Maebe
2011-10-14 14:26 ` Eli Zaretskii
2011-10-14 14:32 ` Jan Kratochvil
2011-10-14 15:05 ` Phil Muldoon
2011-10-14 15:21 ` Eli Zaretskii
2011-10-14 14:52 ` Phil Muldoon
2011-10-14 15:05 ` Eli Zaretskii
2011-10-14 15:47 ` Jonas Maebe
2011-10-14 16:12 ` Andreas Schwab
2011-10-14 16:20 ` Andreas Schwab
2011-10-14 16:25 ` Eli Zaretskii
2011-10-14 17:06 ` Matt Rice
2011-10-14 17:25 ` Eli Zaretskii
2011-11-11 21:00 ` Steinar Bang
2011-11-12 8:30 ` Eli Zaretskii
2011-11-12 15:30 ` Steinar Bang
2011-10-14 5:10 ` Joel Brobecker
2011-10-14 15:38 ` Joseph S. Myers
2011-10-14 12:36 ` André Pönitz
2011-10-14 14:19 ` Eli Zaretskii
2011-10-14 15:02 ` Phil Muldoon
2011-10-14 15:16 ` Eli Zaretskii
2011-10-14 16:59 ` André Pönitz
2011-10-14 14:58 ` Phil Muldoon
2011-10-14 15:02 ` Paul_Koning
2011-10-16 15:04 ` Ralf Corsepius
2011-10-14 16:10 ` André Pönitz
2011-11-11 22:50 ` Pedro Larroy
2011-11-12 8:28 ` Steinar Bang
2011-11-13 0:05 ` John Hein
2011-11-15 15:02 ` Tom Tromey
2011-11-16 16:59 ` Christopher Faylor
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=E1RET3g-0007YR-Kr@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=gdb@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).