Re: crm versions in CVS

On 2008-03-26, Johannes Berg wrote:
> While that is possible, the resulting trees will most likely not be
> mergeable because at some point some slightly different patch
> description will creep in.
 
  I see two points here:
  1. under a dvcs, trees diverge over time and become difficult (sometimes 
impossible) to merge.  This would seem to be a general problem of any 
distributed system, and also one that is media independent.

  2. Slightly different patch descriptions cause problems under git.  I've not 
used git in a multi-person setting, and am not terribly familiar with its 
quirks.  So I really don't know what this means.

  As to problem #1, I don't see how a central server solves it.  Notifies you 
sooner maybe, but doesn't the problem still exist?

  As to problem #2, doesn't this just mean that a naming convention for 
patches needs to be proposed and enforced which makes the names be unique?

  Would these issues be mitigated (or even resolved) if every release also had 
a tarball of the git repository from whence it came, on which developers were 
expected to rebase their local repositories?

  It just seems, at least to me, that for a dvcs which supports patch exchange 
over email, there should be some functional workflow which doesn't require 
anyone to have a central server.  Maybe it requires a little bit more book 
keeping than with a central server, sure.  But it's got to be less book work 
than the devs do now.

~crh

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

_______________________________________________
Crm114-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/crm114-general

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.8 (FreeBSD)

iEYEARECAAYFAkfqeLYACgkQQ/a2GD73knu+OgCeJHfRvF8cPA1+nhDsBERYdG6h
MxgAoMe9m1WlFzxt5zpD/xiokFAk7bsj
=XET2
-----END PGP SIGNATURE-----