> (I'm starting to pay attention to viking again after a hiatus due to
> Things Other than Geo needing time.)
Good news!
> It looks like Rob is now working directly in the SF repo.
Since I have commit privileges, 'simple' fixes / small changes get applied
directly to the SF repo.
This is a maintainer thing as they don't necessarily need any feedback before
being applied.
> I'd like to see a HACKING.git in the official repo that lists all the
> URLs of actively-maintained versions. Sort of like a list of forks,
> but without buying ito any repo service as the one true way.
>
> So, can people explain what counts these days?
I don't think this needs to be in the source, perhaps in the Wiki -
'contribute' part.
> Also, do the maintainer prefer mail with format-patch, or a public repo?
> (With my maintainer hat on for other projects, I want people to publish
> a repo that I can remote add and inspect and maybe merge from.)
Format patch is fine for single commits, as I think it's easy enough for the
maintainer and potentially easier for a contributer (as they don't need a
public repo).
Most changes have come through patches / diffs.
However for more complicated changes requiring a series of commits then
definitely a public repo is best so the code can be reviewed more easily.
> I'd be happy to make a README.git and format-patch/send a commit.
OK, but again I think this meta-data about the code would be better served by
being in the Wiki.
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Viking-devel mailing list
Viking-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/viking-devel
Viking home page: http://viking.sf.net/
