Quoting Peter Suter <petsu...@gmail.com>:
On 03.12.2014 16:40, Christopher Nelson wrote:
On 2014-06-22 12:12, Olemis Lang wrote:
I'm not very fond of git at all , TBH . It does not integrate well
with Trac ,
OT: This is a major problem for Trac. Nothing against hg, but Git
is currently the most successful VCS. If Trac will not improve
its Git support, people will move away from Trac, not from Git.
Could you give more details about what you mean? Why does git not
integrate well? How would improved git support look like? What's
missing that hg has?
Olemis Lang can probably compare git with hg in Trac.
For me, there are two problems:
1. No nice integration. With typical/simple hooks, the same commits
get referenced (#refs) in tickets again and again when merging and
branching. Worse, if you had a commit closed by a commit
(#closes), but had to reopen later, it gets closed again just by a
merge!
What is missing is a list of commits already processed, so that
Trac doesn't list the same commit multiple times. Or a more
flexible approach, e.g. if one maintains ticket specific branches,
link all changes in the respective branch in the ticket, but also
show merges into master or a release branch.
Good hook scripts for different workflows should be part of the
Trac distribution in the contrib directory.
2. Performance for large repositories. Try to import the linux kernel
source and actually use it. It works neither with nor without
cache, it is too slow to use. Cache creation took many hours on my
notebook computer, btw.
Cheers
--
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to trac-dev+unsubscr...@googlegroups.com.
To post to this group, send email to trac-dev@googlegroups.com.
Visit this group at http://groups.google.com/group/trac-dev.
For more options, visit https://groups.google.com/d/optout.
