git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "A.J. Rossini" <blindglobe@gmail.com>
To: "Andy Parkins" <andyparkins@gmail.com>
Cc: git@vger.kernel.org, "Junio C Hamano" <junkio@cox.net>
Subject: Re: Rebasing a branch that contains merges
Date: Mon, 19 Feb 2007 15:39:11 +0100	[thread overview]
Message-ID: <1abe3fa90702190639g3e0d6da1xa8086999ca53228@mail.gmail.com> (raw)
In-Reply-To: <200702191048.24091.andyparkins@gmail.com>

On 2/19/07, Andy Parkins <andyparkins@gmail.com> wrote:

> So - rebase would need some sort of language to tell it which branch to
> favour.

The more I use git, the more I start thinking that a domain-specific
language to describe merges would not be a bad thing.  It's so easy
(painless, thought-free) to create a complex set of branches that
you'd like to rearrange with each other.

Of course, perhaps the right solution is to be simpler and old
fashioned and cease hyper-multitasking (i.e. shooting myself in the
foot).

(I'm sharing Andy's assumption that my repo is just mine, not really
shared -- add in sharing, or public use, and it gets far more complex,
and the language idea might be a good idea, and not just an idea.
Darcs has it's theory of patches, though it's not a language).

best,
-tony

blindglobe@gmail.com
Muttenz, Switzerland.
"Commit early,commit often, and commit in a repository from which we can easily
roll-back your mistakes" (AJR, 4Jan05).

      reply	other threads:[~2007-02-19 14:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-19  9:12 Rebasing a branch that contains merges Andy Parkins
2007-02-19  9:36 ` Junio C Hamano
2007-02-19 10:48   ` Andy Parkins
2007-02-19 14:39     ` A.J. Rossini [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=1abe3fa90702190639g3e0d6da1xa8086999ca53228@mail.gmail.com \
    --to=blindglobe@gmail.com \
    --cc=andyparkins@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).