From: Michal Simek <monstr@seznam.cz>
To: linux-kernel@vger.kernel.org
Subject: microblaze: Merge window + git
Date: Fri, 11 Apr 2008 09:50:21 +0200 [thread overview]
Message-ID: <47FF183D.8060408@seznam.cz> (raw)
Hi everybody,
Can you tell me when is open next merge window?
and my next question is about GIT.
I have second release at my git server and I have some changes which you
reported. I would like to collect all changes in the same set of patches.
I mean I have patch with 4 files and I did next changes. I would like to
integrate these changes to the same patches. Is it possible to do it?
It is easier to review all changes together.
I think it is no good way to send first release with reported bugs and new diffs.
Thanks,
Michal Simek
www.monstr.eu
next reply other threads:[~2008-04-11 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 7:50 Michal Simek [this message]
2008-04-11 10:51 ` microblaze: Merge window + git Stefan Richter
2008-04-11 12:45 ` Ilpo Järvinen
2008-04-12 21:21 ` H. Peter Anvin
2008-04-13 11:32 ` Michal Simek
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=47FF183D.8060408@seznam.cz \
--to=monstr@seznam.cz \
--cc=linux-kernel@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