From: "J. Bruce Fields" <bfields@fieldses.org>
To: Sam Vilain <sam@vilain.net>
Cc: git@vger.kernel.org
Subject: Re: Multi-headed branches (hydra? :)) for basic patch calculus
Date: Sun, 2 Apr 2006 12:11:21 -0400 [thread overview]
Message-ID: <20060402161121.GB18864@fieldses.org> (raw)
In-Reply-To: <1143950852.21233.23.camel@localhost.localdomain>
On Sun, Apr 02, 2006 at 04:07:32PM +1200, Sam Vilain wrote:
> To represent this in git you could just roll back the head merge commit,
> push commit 5 on that branch, then make a new head:
>
> 1 -> 3 -> 5 \
> >- head
> 2 -> 4 -----/
>
> However, if there was support for "hydra", or heads that are multiple
> commit IDs (and necessarily, no blobs in corresponding paths in their
> trees that are not identical), then you would not need to destroy and
> recreate this dummy merge head commit to model your patch history in
> this manner.
What's the advantage to doing this?
> If the plumbing or a porcelain could be smart enough to automatically
> create hydra when patches are not dependent, then many of the benefits
> of patch calculus might come for free, without having to create these
> complicated sounding entities manually.
What are the benefits of patch calculus? (What is it? The only
explanation I've seen is at
http://abridgegame.org/darcs/manual/node8.html, but I don't find it very
helpful.)
--b.
next prev parent reply other threads:[~2006-04-02 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-02 4:07 Multi-headed branches (hydra? :)) for basic patch calculus Sam Vilain
2006-04-02 6:49 ` Jakub Narebski
2006-04-02 23:15 ` Sam Vilain
2006-04-03 4:10 ` Jakub Narebski
2006-04-02 16:11 ` J. Bruce Fields [this message]
2006-04-02 16:30 ` Patch calculus Jakub Narebski
2006-04-02 17:03 ` Jakub Narebski
2006-04-03 1:15 ` Multi-headed branches (hydra? :)) for basic patch calculus Martin Langhoff
2006-04-03 2:09 ` Sam Vilain
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060402161121.GB18864@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=sam@vilain.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).