I spent a good amount of time yesterday figuring out the correct workflow
to submit a change to gitk. As I understand it, gitk (and I think git-gui)
are maintained upstream of git, and patches should be sent to the git email
list against the upstream repo. I think a top-level MAINTAINERS file would
help new contributers like me get orientated, especially in the cases of these
upstream projects that require a somewhat non-standard workflow
I also added some additional clarifications to SubmittingPatches that
clarifies the additional steps required to submit patches against the guis.
Please double check that I've got the correct email addresses and canonical
repositories
I'm guessing there are additional Maintainers who should be added to the
MAINTAINERS file, I just haven't followed to email list closely enough to
know all the formal/informal workflows that should be observed.
Jason Holden (2):
Add top-level maintainers file with email/canonical repository
information
Provide better guidance for submitting patches against git-gui, gitk
Documentation/SubmittingPatches | 11 +++++++++++
MAINTAINERS | 17 +++++++++++++++++
2 files changed, 28 insertions(+)
create mode 100644 MAINTAINERS
--
1.8.1.rc3.28.g0ab5d1f
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
