From: Christopher Li <sparse@chrisli.org>
To: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Sparse official tree merged
Date: Sat, 18 Jul 2009 15:08:28 -0700 [thread overview]
Message-ID: <70318cbf0907181508x3a11d789v79f556ac18fd89ff@mail.gmail.com> (raw)
Hi,
I just clean up the history in chrisl/sparse.git a little bit and
push them to the official tree.
Moving forward, I am going to continue using chrisl/sparse.git
as a developing tree. Patches will first apply there and then
move to official tree later on.
Warning for developing branch, I am going to clean up history there
occasionally.You might not get a clean fast forward pull. If that becomes
a problem, I will consider using topic branch later. For now, there
is just not enough changes to make the topic branch worthwhile.
Please give the official tree some test and report any problem you
found.
Thanks
Chris
reply other threads:[~2009-07-18 22:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=70318cbf0907181508x3a11d789v79f556ac18fd89ff@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=linux-sparse@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;
as well as URLs for NNTP newsgroup(s).