From: Theodore Tso <tytso@mit.edu>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, "Eric S. Raymond" <esr@thyrsus.com>
Subject: Re: Comments on "Understanding Version Control" by Eric S. Raymond
Date: Thu, 5 Feb 2009 08:16:11 -0500 [thread overview]
Message-ID: <20090205131611.GJ8945@mit.edu> (raw)
In-Reply-To: <200902051223.38992.jnareb@gmail.com>
On Thu, Feb 05, 2009 at 12:23:37PM +0100, Jakub Narebski wrote:
> >
> > 2) And does the right thing happen if the situation is as described
> > above, but in, branch C, which is descended from branch B, a new
> > directory, src/plugin/innodb-experimental is created, such that
> > src/plugin/innodb and src/plugin/innodb-experimental both exist.
> > Now the same commit from branch A is pulled into branch C. Will
> > the correct thing happen in that the correct files in
> > src/plugin/innodb are modified and created, even though there is a
> > new directory containing a completely unrelated plugin that happens
> > to have the name, "innodb-experimental"?
>
> Errr... I think that you confused branch 'B' (with innodb-experimental)
> with branch 'A' (with innodb only) here.
>
No, I didn't. Let me try again.
At time T: Project grows a plugin in directory src/plugins/foo-new
At time T+1: Project releases a stable release, and branches off "maint"
At time T+2: Project renames the plugin to be src/plugins/foo, using
"scm mvdir src/plugins/foo-new src/plugins/foo" on the
devel branch:
At time T+3: A developer wants to implement a new experimental
'foo-new' plug in so she creates a completely new
src/plugins/foo-new directory. At this point the
devel branch has 'src/plugins/foo' and
'src/plugins/foo-new', where src/plugins/foo contains
the plugin which is in the directory
src/plugins/foo-new on the maint branch (since the
maint branch branched off
before the directory renames started happening.
At time T+4: A fix goes into the maint branch that modifies
src/plugins/foo-new/interface.c. The fix needs to be
pulled into the devel branch. Does the right thing
happen? (Suppose "interface.c" is a commonly used
filename in all plugins and exists in both the 'foo'
and 'foo-new' directories on the devel branch. Does
the SCM figure out what is the correct file to
modify?)
At Time T+5: A commit goes into the maint branch which creates a
new file, src/plugins/foo-new/table.c, and modifies
src/plugins/foo-new/Makefile to compile table.c.
Which directory does the SCM drop table.c into?
Thie point is if the project is organized around plugins, which are
considered bundles of code written in a modular way, and there is a
desire to rename directories which are the top-level modules, an SCM
that can easily deal with directory renames is important. In practice
this doesn't come up in the Linux kernel, and many other OSS projects,
and if the project's developent style doesn't do directory
reorganizations often, then this isn't an issue. If an OSS project
does do this type of reorganization more frequently, then the argument
"don't do that", would seem to be an unnecessary restriction.
- Ted
next prev parent reply other threads:[~2009-02-05 13:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-02 18:48 Comments on "Understanding Version Control" by Eric S. Raymond Jakub Narebski
2009-02-02 20:24 ` Theodore Tso
2009-02-02 20:35 ` Eric S. Raymond
2009-02-03 20:57 ` Jakub Narebski
2009-02-04 2:04 ` Jakub Narebski
2009-02-04 23:54 ` Theodore Tso
2009-02-05 0:04 ` Junio C Hamano
2009-02-05 2:43 ` Theodore Tso
2009-02-05 6:24 ` Junio C Hamano
2009-02-05 13:28 ` Theodore Tso
2009-02-05 23:06 ` Junio C Hamano
2009-02-05 0:08 ` Jakub Narebski
2009-02-05 0:49 ` Theodore Tso
2009-02-05 6:01 ` Miles Bader
2009-02-05 9:34 ` Eric S. Raymond
2009-02-05 11:23 ` Jakub Narebski
2009-02-05 13:16 ` Theodore Tso [this message]
2009-02-05 17:36 ` Jakub Narebski
2009-02-05 21:45 ` Theodore Tso
2009-02-04 22:14 ` Tests for " Jakub Narebski
2009-02-10 1:20 ` Comments on " Jakub Narebski
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=20090205131611.GJ8945@mit.edu \
--to=tytso@mit.edu \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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 NNTP newsgroup(s).