From: Peter Williams <peter_ono@users.sourceforge.net>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [HELP] Adding git awareness to the darning patch management system.
Date: Thu, 01 Dec 2011 09:47:58 +1000 [thread overview]
Message-ID: <4ED6C0AE.9010703@users.sourceforge.net> (raw)
In-Reply-To: <CALUzUxrcWB62jARtgifTOocGL4gEGXDFMiO=ppHXzFyUmb+3ww@mail.gmail.com>
On 30/11/11 19:04, Tay Ray Chuan wrote:
> On Wed, Nov 30, 2011 at 10:17 AM, Peter Williams
> <peter_ono@users.sourceforge.net> wrote:
>> I'm the author of the darning patch management system
>> <http://darning.sourceforge.net/> and would like some help adding git
>> awareness to the system. At this stage of the development, "awareness" is
>> fairly simple concept with two broad aims:
>
> That link says it "combines the strengths of quilt and mq and
> eliminates their weaknesses", but I don't see any info on why this is
> the case with your program;
Documenting this is on my todo list (but not at the top).
Quilt's weaknesses are documented on their website and my issues with MQ
is that it (potentially) compromises the Mercurial repository and others
to which it may push. (MQ also has the problem that its current
maintainers don't understand the workflow for which it was designed and
are changing it to suit a different workflow.)
The repository compromise issue also applies to stgit.
Other things darning adds are:
1. tracking of copies and renames (not in quilt),
2. tracking changes to files' modes (not in quilt),
3. binary diffs (using git binary diff format for import/export), and
4. help managing addition of trailing whitespace by patches.
> it would be great it if you could provide
> a quick start guide (probably easier to show this with some commands
> in the CLI rather than GUI screenshots).
At this stage, the CLI is really only there to allow me to do script
based testing of darning's internals and is not a fully capable
interface. However, if you look in the directory test-cli for files
with a ".test" suffix you will find examples of their use.
>
> Have a look at StGit's tutorial
> http://www.procode.org/stgit/doc/tutorial.html (very similar to quilt
> and mq too) to see what I mean.
OK
Peter
prev parent reply other threads:[~2011-12-01 2:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 2:17 [HELP] Adding git awareness to the darning patch management system Peter Williams
2011-11-30 7:22 ` Jeff King
2011-12-01 0:56 ` Peter Williams
2011-12-01 6:27 ` Jeff King
2011-12-01 23:32 ` Peter Williams
2011-12-01 23:40 ` Jeff King
2011-11-30 9:04 ` Tay Ray Chuan
2011-11-30 23:47 ` Peter Williams [this message]
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=4ED6C0AE.9010703@users.sourceforge.net \
--to=peter_ono@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=rctay89@gmail.com \
/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).