[Dune-devel] [Dune] DUNE migration to Git complete
Christian Engwer
christian.engwer at uni-muenster.de
Mon May 6 15:01:19 CEST 2013
Hi Steffen,
> - Carsten brought up the idea of requiring editor hints in new (C++) files. Adding that to the hooks would
> take about five minutes, but what is the general opinion regarding this feature?
I'm in favour of such a rule. I think we should try to enforce as many
style rules as possible, when ever we can agree on a certain rule.
> - In order to mirror our repositories on GitHub, I set up an organizational account called dune-project.
> Currently I am the sole owner of the organization, but I'll gladly add other developers. Just let me know
> and tell me your GitHub account name. I'll also add you to the alias for the associated email account
> (github at dune-project.org).
Why would we need a github mirror? And what about gitorious, launchpad
etc.? Do we really want to do this?
> - We should really encourage users to send us patches via pull request (preferred) or, if that is not possible
> for some reason, via "git format-patch". Apart from saving the person applying the patch a lot of work, this
> also has the additional advantage of preserving the committer (for pull requests) or at least author (for
> "git format-patch") information. With that information in the repository it should become a lot easier to compile
> stuff like lists of external contributors in the future.
agree
Ciao
Christian
More information about the Dune-devel
mailing list