archive mirror
 help / color / mirror / Atom feed
* workflow
@ 2021-05-09  7:33 Fabio Aiuto
  2021-05-09  9:31 ` workflow Geert Stappers
  2021-05-09 12:13 ` workflow Miguel Ojeda
  0 siblings, 2 replies; 5+ messages in thread
From: Fabio Aiuto @ 2021-05-09  7:33 UTC (permalink / raw)
  To: rust-for-linux

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

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,


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2021-05-09 17:37 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-05-09  7:33 workflow Fabio Aiuto
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

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).