From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Reintegrate script
Date: Mon, 26 Jan 2009 12:18:30 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.1.00.0901261218070.14855@racer> (raw)
In-Reply-To: <7vd4ea8mnf.fsf@gitster.siamese.dyndns.org>
Hi,
On Mon, 26 Jan 2009, Junio C Hamano wrote:
> In a workflow that uses topic branches heavily, you would need to keep
> updating test integration branch(es) all the time. If they are managed
> like my 'next' by merging the tips of topics that have grown since the
> last integration, it is not so difficult. You only need to review
> output from "git branch --no-merged next" to see if there are topics
> that can and needs to be merged to 'next'.
>
> But sometimes it is easier to rebuild a test integration branch from
> scratch all the time, especially if you do not publish it for others to
> build on.
FWIW that is exactly what I am aiming at with my rebase -i -p work.
Ciao,
Dscho
next prev parent reply other threads:[~2009-01-26 11:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 9:03 [PATCH] Reintegrate script Junio C Hamano
2009-01-26 11:18 ` Johannes Schindelin [this message]
2009-02-13 18:23 ` [PATCH] Meta/Reintegrate: Record all merges to prevent losing topics Bernt Hansen
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=alpine.DEB.1.00.0901261218070.14855@racer \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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