From: Andreas Ericsson <ae@op5.se>
To: Sam Vilain <sam@vilain.net>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: n-heads and patch dependency chains
Date: Tue, 04 Apr 2006 11:28:50 +0200 [thread overview]
Message-ID: <44323C52.2030803@op5.se> (raw)
In-Reply-To: <4431B60E.3030008@vilain.net>
Sam Vilain wrote:
> Junio C Hamano wrote:
>
>>For example, the point jdl raised during the discussion is far
>>easier to understand. When working on multiple topics, he often
>>needs to test them as a whole, so he pulls them into a test
>>branch (can be a throwaway branch). When he needs to do fixups,
>>it is most efficient to do compile/run test while still in the
>>test branch, but after things test out, in order to keep
>>logically different things separate, he needs to go back to
>>relevant topic branches and make a commit. This is painful --
>>are there ways to make this easier [*2*]?
>>
>>Would patch commutation calculus help with his problem?
>>
>>
>
>
> I'd provisionally say "yes, that's the fit". It's just like having
> multiple topic branches all checked out at once, with commits going to
> the appropriate branch as necessary.
>
Wouldn't "git commit -M -b topic", for committing to a different branch
than what is checked out (-b) and also to the checked out branch (-M)
have the same beneficial effects, but without the complexity of hydras
and patch dependency theory? It would only remove the cherry-pick stage
though, but perhaps it's good enough. Although when I think about it, -b
<branch> for committing to another branch and -B <branch> for doing the
above probably makes more sense.
Those flags don't exist currently btw, in case someone's reading this on
the archives.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-04-04 9:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-03 7:48 n-heads and patch dependency chains Sam Vilain
2006-04-03 14:29 ` Linus Torvalds
2006-04-03 15:38 ` Sam Vilain
2006-04-03 19:37 ` Junio C Hamano
2006-04-03 23:55 ` Sam Vilain
2006-04-04 9:28 ` Andreas Ericsson [this message]
2006-04-04 9:51 ` Junio C Hamano
2006-04-04 10:44 ` Andreas Ericsson
2006-04-04 11:03 ` Jakub Narebski
2006-04-04 11:47 ` Andreas Ericsson
2006-04-20 18:08 ` Jon Loeliger
2006-04-20 18:55 ` Junio C Hamano
2006-04-21 8:50 ` Andreas Ericsson
2006-04-04 19:00 ` Junio C Hamano
2006-04-04 20:18 ` Jakub Narebski
2006-04-05 6:34 ` Sam Vilain
2006-04-05 7:11 ` Jakub Narebski
2006-04-05 7:31 ` Sam Vilain
2006-04-05 7:59 ` Jakub Narebski
2006-04-04 0:51 ` Jakub Narebski
2006-04-04 11:05 ` Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2006-04-03 22:13 linux
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=44323C52.2030803@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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).