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.
I forgot to mention I agree this is very important for Trac. But I don't
use Git much myself and such improvements must be driven by users and
their experience.
Thanks for sharing your experience.
On 04.12.2014 10:40, W. Martin Borgert wrote:
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.
I also agree that including good scripts would be great. The current
situation seems confusing.
I suspect Jun's scripts in #10730 [1] are already much better than the
alternatives, so I hope people try them and discuss which scripts are
recommended and should be included in Trac.
[1] http://trac.edgewall.org/ticket/10730#comment:11
--
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.
