git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yann Dirson <ydirson@altern.org>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/5] [DRAFT] StGIT, remotes, and parent information
Date: Sat, 27 Jan 2007 12:21:11 +0100	[thread overview]
Message-ID: <20070127104024.16475.81445.stgit@gandelf.nowhere.earth> (raw)

Although they are not finished, it may be useful to give some context
to current threads to publish a snapshot of what I'm working on, so
here it is.

1/5 Move identification of parent branch's remote def up into stack class.

Mostly code reorg.

2/5 Allows extraction of information about remotes.

Introduces a handful of functions to get informations about remotes in
the repository.  Makes use of remote.<branch>.fetch multi-valued
config entry.

3/5 Basic support for keeping a ref to the parent branch.

Currently relies on the failed assumption that config.set() does what
it sounds, so rely instead on a rewritten config.py.

That's why I'd rather rewrite it rapidly without a dictionnary, at
least as a first step - we can make the implementation better
afterwards, but first make it work.  Indeed I was originally only
working on the 5th patch of this stack, and all this is already a bit
beyond of what I was envisonning...

4/5 Have 'stg branch --create' record parent information.

Putting this all together.  Would also need to do something similar in
'stg clone' and possibly other places, so some code surely needs to be
factorized.

5/5 Make 'stg pull' use git-fetch and not git-pull.

Unfinished.  Git-fetch takes care of using the remote information.
Still have to use the previous work to find out the parent branch name
to rebase onto.

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/>

             reply	other threads:[~2007-01-27 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-27 11:21 Yann Dirson [this message]
2007-01-27 11:21 ` [PATCH 1/5] Move identification of parent branch's remote def up into stack class Yann Dirson
2007-01-27 11:21 ` [PATCH 2/5] Allows extraction of information about remotes Yann Dirson
2007-01-27 11:21 ` [PATCH 3/5] Basic support for keeping a ref to the parent branch Yann Dirson
2007-01-27 11:21 ` [PATCH 4/5] Have 'stg branch --create' record parent information Yann Dirson
2007-01-27 11:21 ` [PATCH 5/5] Make 'stg pull' use git-fetch and not git-pull 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=20070127104024.16475.81445.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).