linux-kbuild.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sedat Dilek <sedat.dilek@gmail.com>
To: Michal Marek <mmarek@suse.cz>
Cc: linux-kbuild@vger.kernel.org
Subject: kbuild Git tree and its branches
Date: Sat, 3 Jan 2015 11:28:44 +0100	[thread overview]
Message-ID: <CA+icZUVTgtSxiYz98nB30u05mzc_exLFhUttFkGwvF58sigx5Q@mail.gmail.com> (raw)

Hi Marek,

can you enlighten me about the usage of your Git tree and its branches?
For me this is a bit unclear.

Looking into the Trees file from Linux-next I see
***kbuild.git#rc-fixes*** [1,3] and ***kbuild.git#for-next*** [2,4]...

#7: kbuild-current git
git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git#rc-fixes

#111: kbuild git
git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild.git#for-next

Recently I reported some kbuild issues and sent out some own patches
which were pushed or pending.
This stuff is partly in kbuild.git#misc [5] and kbuild.git#kbuild [6].

Are those branches for mainline?
For example, I have seen git-pull request for "misc" stuff [7].

Finally, my question which of your trees are for mainline aka upstream
(Git) or so-called "Linus tree" [8]?
( I would have expected some of the recent commits for "misc" and
"kbuild" to be pulled in "rc-fixes" - this reflects the usage of
"kbuild-current" in Linux-next for me. )

Maybe, you can tell me how your "daily" kbuild workflow is done.
( I am not ashamed to see I have not checked Documentation directory
in Linux source. ]

Thanks for answering my questions in advance.

Regards,
- Sedat -

[1] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/Next/Trees?id=next-20150103#n7
[2] http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/Next/Trees?id=next-20150103#n111
[3] http://git.kernel.org/cgit/linux/kernel/git/mmarek/kbuild.git/log/?h=rc-fixes
[4] http://git.kernel.org/cgit/linux/kernel/git/mmarek/kbuild.git/log/?h=for-next
[5] http://git.kernel.org/cgit/linux/kernel/git/mmarek/kbuild.git/log/?h=misc
[6] http://git.kernel.org/cgit/linux/kernel/git/mmarek/kbuild.git/log/?h=kbuild
[7] https://lkml.org/lkml/2014/12/19/354
[8] http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git

             reply	other threads:[~2015-01-03 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-03 10:28 Sedat Dilek [this message]
2015-01-05 10:08 ` kbuild Git tree and its branches Michal Marek
2015-01-05 18:35   ` Sedat Dilek

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=CA+icZUVTgtSxiYz98nB30u05mzc_exLFhUttFkGwvF58sigx5Q@mail.gmail.com \
    --to=sedat.dilek@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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).