From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Yann Dirson" <ydirson@altern.org>
Cc: git@vger.kernel.org
Subject: Re: [StGIT PATCH 2/4] Abstract a PatchSet object out of Series.
Date: Tue, 12 Jun 2007 23:09:50 +0100 [thread overview]
Message-ID: <b0943d9e0706121509j5088e164iadedb561501d6a55@mail.gmail.com> (raw)
In-Reply-To: <20070611003330.4736.69293.stgit@gandelf.nowhere.earth>
On 11/06/07, Yann Dirson <ydirson@altern.org> wrote:
> The goal is to move into PatchSet all functionnality that is not
> dependant of Series being a real stack, paving the way for handling
> parallel (hydra) stacks, or any other way to organize patches.
Thanks for the patches. I applied this one as well and I like the
idea. What is your long-term plan with this split?
The HEAD in my repository fails the test suite. Do you have any
additional patches pending (some patches were not applied in order as
I had to manually fix the conflicts). Anyway, please check my
repository for any missing patches.
Thanks.
--
Catalin
next prev parent reply other threads:[~2007-06-12 22:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 0:33 [StGIT PATCH 0/4] Cleanups of the Series object Yann Dirson
2007-06-11 0:33 ` [StGIT PATCH 1/4] Use get/set_name for a stack's name Yann Dirson
2007-06-11 0:33 ` [StGIT PATCH 2/4] Abstract a PatchSet object out of Series Yann Dirson
2007-06-12 22:09 ` Catalin Marinas [this message]
2007-06-13 20:38 ` Yann Dirson
2007-06-14 21:30 ` StGIT rebasing safeguard Yann Dirson
2007-06-19 22:12 ` Catalin Marinas
2007-06-19 22:18 ` Catalin Marinas
2007-06-19 22:37 ` Yann Dirson
2007-06-14 22:56 ` [StGIT PATCH 2/4] Abstract a PatchSet object out of Series Catalin Marinas
2007-06-15 20:14 ` Yann Dirson
2007-06-19 22:32 ` Catalin Marinas
2007-06-11 0:33 ` [StGIT PATCH 3/4] Move stack format-version checks into Stack class Yann Dirson
2007-06-11 0:33 ` [StGIT PATCH 4/4] Rename branch.*.stgitformatversion to branch.*.stgit.stackformatversion Yann Dirson
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=b0943d9e0706121509j5088e164iadedb561501d6a55@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--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).