From: Geert Stappers <stappers@stappers.nl>
To: rust-for-linux@vger.kernel.org
Subject: Re: workflow
Date: Sun, 9 May 2021 11:31:50 +0200 [thread overview]
Message-ID: <20210509093150.jtaizeq5dyyot3qx@gpm.stappers.nl> (raw)
In-Reply-To: <20210509073338.GA1428@agape.jhs>
On Sun, May 09, 2021 at 09:33:38AM +0200, Fabio Aiuto wrote:
> Good morning all,
Hail all time zones,
> I need some clarifications about the workflow.
>
> As a newcomer in kernel development and open source development
> in general I got a little used to with the forkflow in Greg's staging
> subsystem.
>
> The tool I'm used to work with is, at the moment, command line git
> against Greg's tree.
>
> I tried to apply the same approach on rust-for-linux tree but I noticed
> some differences, first of all the use of GitHub.
>
> One misterious to me side effect is that the command `git show` on HEAD
> pointing to a PR doesn't show diffs.
>
> After these two enlightening informal meetings I realized that, for this
> particular project, I must (and I'm happy to do it) align with you all
> using GitHub. Is there a particular join procedure you recommend?
I think original poster
is not aware of "Rust for Linux" already in the next branch.
> thank you,
My appology for this way too short message.
> fabio
Groeten
Geert Stappers
--
Silence is hard to parse
next prev parent reply other threads:[~2021-05-09 9:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 7:33 workflow Fabio Aiuto
2021-05-09 9:31 ` Geert Stappers [this message]
2021-05-09 10:42 ` workflow Fabio Aiuto
2021-05-09 12:13 ` workflow Miguel Ojeda
2021-05-09 17:37 ` workflow Fabio Aiuto
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=20210509093150.jtaizeq5dyyot3qx@gpm.stappers.nl \
--to=stappers@stappers.nl \
--cc=rust-for-linux@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).