From: Fabio Aiuto <fabioaiuto83@gmail.com>
To: rust-for-linux@vger.kernel.org
Subject: workflow
Date: Sun, 9 May 2021 09:33:38 +0200 [thread overview]
Message-ID: <20210509073338.GA1428@agape.jhs> (raw)
Good morning all,
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?
thank you,
fabio
next reply other threads:[~2021-05-09 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 7:33 Fabio Aiuto [this message]
2021-05-09 9:31 ` workflow Geert Stappers
2021-05-09 10:42 ` workflow Fabio Aiuto
2021-05-09 12:13 ` workflow Miguel Ojeda
2021-05-09 17:37 ` workflow Fabio Aiuto
-- strict thread matches above, loose matches on Subject: below --
2019-05-09 14:11 Workflow Thomas Gleixner
2019-05-09 14:45 ` Workflow Kate Stewart
2019-05-09 21:56 ` Workflow Thomas Gleixner
2019-05-10 9:25 ` Workflow Allison Randal
2019-05-10 10:54 ` Workflow Thomas Gleixner
2019-05-10 11:02 ` Workflow Allison Randal
2019-05-10 13:01 ` Workflow Kate Stewart
2019-05-10 13:18 ` Workflow Bradley M. Kuhn
2019-05-10 9:06 ` Workflow Greg KH
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=20210509073338.GA1428@agape.jhs \
--to=fabioaiuto83@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.