From: "Ping Yin" <pkufranky@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: What is the whole process of cooking git as a maintainer?
Date: Wed, 21 Nov 2007 21:17:59 +0800 [thread overview]
Message-ID: <46dff0320711210517y282643a2q62819d3583ec9344@mail.gmail.com> (raw)
In-Reply-To: <46dff0320711210511g7d9febf5k47b082cc13bb905a@mail.gmail.com>
On Nov 21, 2007 9:11 PM, Ping Yin <pkufranky@gmail.com> wrote:
> I have scanned the manual and found a 'Linux subsystem maintainer'
> example. However, that's a little brief and i wonder a more real
> example. I think an example of how to cook git as a maintainer is
> better.
>
> Junio , could you please share the whole process of cooking among pu,
> next and master? Or, can i find this in the mail list archive?
>
> For example:
> In which branch the test is performed?
> How to rewind pu?
> How to merge a subset of changes from pu to next, and from next to master?
>
One more question:
I see so many merges in pu branch, but where these merges go when a
feature is moved to the master branch?
>
> --
> Ping Yin
>
--
Ping Yin
next prev parent reply other threads:[~2007-11-21 13:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 13:11 What is the whole process of cooking git as a maintainer? Ping Yin
2007-11-21 13:17 ` Ping Yin [this message]
2007-11-21 14:07 ` Theodore Tso
2007-11-21 14:45 ` Johannes Schindelin
2007-11-22 0:32 ` Addendum to "MaintNotes" Junio C Hamano
2007-11-22 10:36 ` Jeff King
2007-11-22 10:42 ` Junio C Hamano
2007-11-22 10:48 ` David Kastrup
2007-11-22 11:09 ` Jeff King
2007-11-22 11:08 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46dff0320711210517y282643a2q62819d3583ec9344@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=git@vger.kernel.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.
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 NNTP newsgroup(s).