From: Philippe Fremy <phil@freehackers.org>
To: linux-kernel@vger.kernel.org
Subject: Patching / Merging tool
Date: Sat, 23 Apr 2005 11:27:04 +0200 [thread overview]
Message-ID: <426A14E8.6080005@freehackers.org> (raw)
Hi
For years, I have been willing to write a good patching/merging tool. In
my understanding, the kernel is the most patching/merging demanding
project and now that bitkeeper is gone, there is a hole to be filled.
What would be the requirements for a good patching/merging tool in your
opinion ? What are the use cases ?
How much of integration is required with the SCM, git in the kernel case ?
I am not subscribed, so please CC: me any response.
best regards,
Philippe
next reply other threads:[~2005-04-23 9:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-23 9:27 Philippe Fremy [this message]
2005-04-23 10:45 ` Patching / Merging tool James Purser
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=426A14E8.6080005@freehackers.org \
--to=phil@freehackers.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