I'm a bit confused by the etiquette around submitting
proposals for patches in Git and I would like to
understand this process better. Especially since the
only way to get closure on .gitconfig issue seems to
be to show the code ;-)
Anyway, here are the questions:
0. Junio, are you the only Git maintainer or are there
others responsible for particular subsystems of Git?
1. What's the official way of submitting a patch?
Is git-send-email(1) to this mailing list
good enough? Does a submitter have to have
a public tree that maintainer(s) can pull from?
2. Once the patch is submitted how does the author
get notified whether it is accepted, rejected
or needs additional work.
Now, #2 is especially important for me, simply because
the project I come from (FFmpeg) has a bit of different
policy around the status of each submitted patch.
Pretty much within a 48 hour window a submitter gets
notified whether the patch was accepted, rejected, needs
more work or the maintainer of a particular subsystem needs
more time in order to review the changes. What's confusing to
me with Git, are the examples like some patches from Ping Yin
not receiving any public acknowledgment at all and some of the
patches from other submitters (Dmitry Potapov) getting sort of
lost.
Thanks,
Roman.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
