From: Yann Dirson <ydirson@altern.org>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/7] StGIT, remotes, and parent
Date: Tue, 30 Jan 2007 00:05:19 +0100 [thread overview]
Message-ID: <20070129230117.7102.64322.stgit@gandelf.nowhere.earth> (raw)
This new series should bring the first 5 patches into sufficiently
reasonable shape, so I'm presenting them for inclusion. The last 2
ones are still there for context only.
This new revision of the series brings:
- Better use of stgit.config in subsequent patches, notably deported
the remaining call to repo-config into stgit.config:
config.sections_matching(regexp)
- Caching in stgit.config. I implemented this as on-demand caching,
initially because it was straightforward, but it turns out that
sections_matching() naturally fits in this model, and i'm not sure how
we could have implemented this in the pre-caching model.
- The usual bunch of misc cleanups.
Best regards,
--
Yann Dirson <ydirson@altern.org> |
Debian-related: <dirson@debian.org> | Support Debian GNU/Linux:
| Freedom, Power, Stability, Gratis
http://ydirson.free.fr/ | Check <http://www.debian.org/>
next reply other threads:[~2007-01-29 23:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 23:05 Yann Dirson [this message]
2007-01-29 23:05 ` [PATCH 1/7] Make stgit.config use git-repo-config Yann Dirson
2007-01-29 23:05 ` [PATCH 2/7] Add caching to the new config class Yann Dirson
2007-01-29 23:05 ` [PATCH 3/7] Move identification of parent branch's remote def up into stack class Yann Dirson
2007-01-29 23:05 ` [PATCH 4/7] Allows extraction of information about remotes Yann Dirson
2007-01-29 23:05 ` [PATCH 5/7] Basic support for keeping a ref to the parent branch Yann Dirson
2007-01-29 23:05 ` [PATCH 6/7] Have 'stg branch --create' record parent information Yann Dirson
2007-01-29 23:05 ` [PATCH 7/7] Make 'stg pull' use git-fetch and not git-pull Yann Dirson
2007-01-31 23:44 ` Catalin Marinas
2007-02-01 18:47 ` 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=20070129230117.7102.64322.stgit@gandelf.nowhere.earth \
--to=ydirson@altern.org \
--cc=catalin.marinas@gmail.com \
--cc=git@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).