From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "David Kågedal" <davidk@lysator.liu.se>,
"Git Mailing List" <git@vger.kernel.org>,
"Yann Dirson" <ydirson@altern.org>
Subject: Re: [StGit RFC] A more structured way of calling git
Date: Sat, 3 Nov 2007 10:56:36 +0000 [thread overview]
Message-ID: <b0943d9e0711030356j4dcd31cbl54d838107240b3d0@mail.gmail.com> (raw)
In-Reply-To: <20071026192418.GA19774@diana.vm.bytemark.co.uk>
On 26/10/2007, Karl Hasselström <kha@treskal.com> wrote:
> I wanted to build an StGit command that coalesced adjacent patches to
> a single patch. Because the end result tree would still be the same,
> this should be doable without ever involving HEAD, the index, or the
> worktree.
Wouldn't HEAD need to be modified since the commit log changes
slightly, even though the tree is the same. Or am I misunderstanding
this?
> StGit's existing infrastructure for manipulating patches
> didn't lend itself to doing this kind of thing, though: it's not
> modular enough. So I started to design a replacement low-level
> interface to git, and things got slightly out of hand ... and I ended
> up with a much bigger refactoring than I'd planned.
Thanks for this. I'll need a bit of time to read it all and give
feedback. In general, I welcome this refactoring.
I'll go through the whole e-mail in the next days and get back to you.
--
Catalin
next prev parent reply other threads:[~2007-11-03 10:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 19:24 [StGit RFC] A more structured way of calling git Karl Hasselström
2007-11-03 10:56 ` Catalin Marinas [this message]
2007-11-03 14:28 ` Yann Dirson
2007-11-04 18:40 ` Karl Hasselström
2007-11-04 18:34 ` Karl Hasselström
2007-11-15 18:28 ` Catalin Marinas
2007-11-16 7:42 ` Karl Hasselström
2007-11-16 8:36 ` Karl Hasselström
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=b0943d9e0711030356j4dcd31cbl54d838107240b3d0@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=davidk@lysator.liu.se \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=ydirson@altern.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).