[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: git copies of cvs modules available
On Tue, Jan 12, 2010 at 05:38:13PM +0900, Curt Sampson wrote:
> > > It is not surprising that like cvs git
> > > requires a service of its own to work properly,
> > UNlike cvs, unless you want to name ssh 'a service of its own'.
> Perhaps he should have appended, "when not being used over ssh" to that
> statement. Both cvs and git work just fine without anything special
> installed if the user has shell access via ssh to the host that contains
> the repository. Both also need a special service and protocol for users
> that do not have shell access to that host.
Perhaps this would be the point to note that Mercurial's preferred
remote update service requires only http and a cgi script...
btw, does this whole thread have to be cc'd to current-users?
> Actually, that can be fixed in the conversion tool relatively easily.
> The bigger problem is, how do we keep doing keyword expansion if we
> switch to git?
> These days, my preference would be to kill it. It makes me nervous that
> a checkout of a particular revision is not what's in the repository for
> that particular revision, but instead a modified copy whose particular
> modifications may change when the VCS software changes.
It is nonetheless desirable to be able to ident binaries.
David A. Holland
Main Index |
Thread Index |