From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Yann Dirson" <ydirson@altern.org>
Cc: git@vger.kernel.org
Subject: Re: [StGIT RFC PATCH 0/2] Fixing the rebase safeguard
Date: Mon, 4 Jun 2007 23:41:36 +0100 [thread overview]
Message-ID: <b0943d9e0706041541i74f5dccct9f66a7dca1f1ffea@mail.gmail.com> (raw)
In-Reply-To: <20070603133006.1681.1742.stgit@gandelf.nowhere.earth>
On 03/06/07, Yann Dirson <ydirson@altern.org> wrote:
> This is an attempt at using a reachability test to replace the use of
> orig-base, to decide when it is safe to accept a rebase.
[...]
> - using ORIG_HEAD, but then, how do we decide when it is valid to do
> so ?
I think using the ORIG_HEAD was the initial behaviour of StGIT. I
didn't have any problems as I am only following one tree (Linus'
mainline kernel) but other users might have different scenarios.
--
Catalin
prev parent reply other threads:[~2007-06-04 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 13:41 [StGIT RFC PATCH 0/2] Fixing the rebase safeguard Yann Dirson
2007-06-03 13:41 ` [PATCH 1/2] Changed rebasing safety check to look for reachability of stack base (gna bug #9181) Yann Dirson
2007-06-04 13:42 ` David Kågedal
2007-06-03 13:41 ` [PATCH 2/2] Test "stg rebase" after "stg commit" Yann Dirson
2007-06-04 22:41 ` Catalin Marinas [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=b0943d9e0706041541i74f5dccct9f66a7dca1f1ffea@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).