From: Artem Bityutskiy <dedekind@yandex.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: -mm tree and git
Date: Fri, 08 Dec 2006 15:47:37 +0200 [thread overview]
Message-ID: <45796CF9.3050702@yandex.ru> (raw)
Hello Andrew, community,
I am not really aware how your -mm tree cooperates with git so I have
questions.
Actually I am talking about the "git-ubi.patch" in your tree. You seems
to periodically update the patch by fetching the stuff from the
ubi-2.6.git GIT tree.
1. How do you produce the diff file from the ubi-2.6.git?
2. Do you mind if I re-base the ubi-2.6.git from time to time? Does it
cause any troubles for you?
3, Are there some special things I should or should not do to make it
easy for you to work with the git tree?
4. I see a
"ubi-versus-add-include-linux-freezerh-and-move-definitions-from.patch"
patch in your tree. It is related to the stuff which is available in
Linus's tree. But my tree does not have it yet. Is is OK if I won't push
it for now and do this later when I sync with mainline?
Thanks.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next reply other threads:[~2006-12-08 13:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 13:47 Artem Bityutskiy [this message]
2006-12-08 20:50 ` -mm tree and git Andrew Morton
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=45796CF9.3050702@yandex.ru \
--to=dedekind@yandex.ru \
--cc=akpm@osdl.org \
--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