From: Robert Buck <buck.robert.j@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: newbie: need concrete examples for how the linux-kernel project uses git
Date: Tue, 4 May 2010 22:11:03 -0400 [thread overview]
Message-ID: <k2l408104421005041911t32652fb7ie9618a301d998983@mail.gmail.com> (raw)
In-Reply-To: <20100505011045.GA16345@progeny.tock>
Wow, this is really great folks. Let me look at these links again.
Great stuff. Thank you,
-Bob
On Tue, May 4, 2010 at 9:10 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Hi Robert,
>
> Robert Buck wrote:
>
>> We have multiple teams, lots of developers, and would like to use a
>> variant of the dictator-lieutenant scheme discussed in published
>> subject matter.
>>
>> However, I find it rather challenging finding any subject matter that
>> provides reasonable detail.
>
> Probably you have run into these already. But for reference...
>
> To be a maintainer:
>
> - the gitworkflows(7) page[1]
>
> The kernel does not follow all of these practices, but maybe similar
> projects could benefit from some. :)
>
> To be a “leaf” contributor (does not require git):
>
> - the Linux wireless git guide[2]
> - submitting patches to linux-wireless.git[3]
> - guide to tip.git (Linux’s x86 architecture support subsystem) [4]
>
> To build a throw-away integration branch:
>
> - Stephen Rothwell’s linux-next tree[5]
>
> To be, well, anyone:
>
> - “everyday git in 20 commands or so” [6]
>
> Patch flow:
>
> - for Linux wireless [7]
> - for git [8]
>
> Separate “internal use” and “public” trees:
>
> - nouveau/linux-2.6 [9]
>
>> What I'd like to find are concrete
>> examples, step-by-step, of specifically how to:
>
> If you find these, information for each about
>
> - where you expected to find it
> - where you actually found it
> - how helpful that information was
>
> would be very useful. It would be nice to be able to update “everyday git”,
> the user manual, the reference manual pages, and other documents to make
> this sort of question easier to answer.
>
> Hope that helps,
> Jonathan
>
> [1] http://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html
> [2] http://wireless.kernel.org/en/developers/Documentation/git-guide
> [3] http://wireless.kernel.org/en/developers/Documentation/SubmittingPatches
> [4] http://people.redhat.com/mingo/tip.git/readme.txt
> [5] http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=tree;f=Next
> [6] http://www.kernel.org/pub/software/scm/git/docs/everyday.html
> [7] http://wireless.kernel.org/en/developers/process
> [8] https://git.wiki.kernel.org/index.php/MaintNotes
> [9] http://lists.freedesktop.org/archives/nouveau/2009-March/002765.html
> http://cgit.freedesktop.org/nouveau/linux-2.6/
> ‘git rebase’ is the main tool here.
>
next prev parent reply other threads:[~2010-05-05 2:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-04 21:31 newbie: need concrete examples for how the linux-kernel project uses git Robert Buck
2010-05-05 1:09 ` Jeff King
2010-05-05 1:10 ` Jonathan Nieder
2010-05-05 2:11 ` Robert Buck [this message]
2010-05-05 3:36 ` Lin Mac
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=k2l408104421005041911t32652fb7ie9618a301d998983@mail.gmail.com \
--to=buck.robert.j@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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).