From: Junio C Hamano <gitster@pobox.com>
To: Jason Holden <jason.k.holden.swdev@gmail.com>
Cc: git@vger.kernel.org, paulus@samba.org, patthoyts@users.sourceforge.net
Subject: Re: [PATCH 0/2] Add MAINTAINERS file and clarify gui workflows
Date: Sun, 30 Dec 2012 12:26:39 -0800 [thread overview]
Message-ID: <7va9svffr4.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <1356891535-5647-1-git-send-email-jason.k.holden.swdev@gmail.com> (Jason Holden's message of "Sun, 30 Dec 2012 13:18:53 -0500")
Jason Holden <jason.k.holden.swdev@gmail.com> writes:
> I spent a good amount of time yesterday figuring out the correct workflow
> to submit a change to gitk.
Thanks; I just realized that nothing in Documentation/ hierarchy
mentions these; they are only mentioned in "A Note from the
Maintainer" I send out every once in a while (kept in MaintNotes of
'todo' branch):
* Other people's trees, trusted lieutenants and credits.
Documentation/SubmittingPatches outlines to whom your proposed changes
should be sent. As described in contrib/README, I would delegate fixes
and enhancements in contrib/ area to the primary contributors of them.
Although the following are included in git.git repository, they have their
own authoritative repository and maintainers:
- git-gui/ comes from git-gui project, maintained by Pat Thoyts:
git://repo.or.cz/git-gui.git
- gitk-git/ comes from Paul Mackerras's gitk project:
git://ozlabs.org/~paulus/gitk
- po/ comes from the localization coordinator, Jiang Xin:
https://github.com/git-l10n/git-po/
Perhaps the update should mention po/ as well?
next prev parent reply other threads:[~2012-12-30 20:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 18:18 [PATCH 0/2] Add MAINTAINERS file and clarify gui workflows Jason Holden
2012-12-30 18:18 ` [PATCH 1/2] Add top-level maintainers file with email/canonical repository information Jason Holden
2012-12-30 18:18 ` [PATCH 2/2] Provide better guidance for submitting patches against git-gui, gitk Jason Holden
2012-12-30 20:26 ` Junio C Hamano [this message]
2012-12-31 9:40 ` [PATCH 0/2] Add MAINTAINERS file and clarify gui workflows Thomas Ackermann
2012-12-31 18:22 ` Jason Holden
2012-12-31 18:32 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7va9svffr4.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jason.k.holden.swdev@gmail.com \
--cc=patthoyts@users.sourceforge.net \
--cc=paulus@samba.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).