From: Jan Nieuwenhuizen <janneke-list@xs4all.nl>
To: Jonathan Nieder <jrnieder@uchicago.edu>
Cc: git <git@vger.kernel.org>, Jan Holesovsky <kendy@suse.cz>
Subject: Re: [TopGit PATCH] tg-create.sh: Introduce --add option to add a dependency.
Date: Fri, 15 Aug 2008 10:10:34 +0200 [thread overview]
Message-ID: <1218787834.7585.13.camel@heerbeest> (raw)
In-Reply-To: <Pine.GSO.4.62.0808131100280.1278@harper.uchicago.edu>
On wo, 2008-08-13 at 11:20 -0500, Jonathan Nieder wrote:
Hi,
> Interesting - I had imagined changing dependencies working in an
> entirely different way.
Thanks! This is quite interesting. A few questions
>
> $ git checkout -b P' P
> $ git rebase --onto B' B
.. is using rebase a robust solution? We should provide a way to
recover after user intervention here?
> $ git checkout P
> $ git merge --no-ff --no-commit B' (*)
Do you remember in what area the problem is here, that would make it a
lot easier for me to look.
> $ git read-tree -u P'
Ouch, I'm feeling so git-unitiated here; what is read-tree doing
differently from merge? Isn't here a -m missing?
> The main problem I see with this story is that if B' is just B with some
> new changes added this is overly complicated.
Yes, that's my main gripe. One of the use cases I'm looking at is
our ooo-build master branch; which includes ~300 topic branches.
Removing or [re-]adding one dependency using this rebase-by-merging
approch would take ~7 minutes on my machine.
I'm now also looking at a .topundeps file, to support
the re-adding of a depenency using the cherry-pick approach...
Greetings,
Janneke.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
next prev parent reply other threads:[~2008-08-15 8:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 14:25 [TopGit PATCH] tg-create.sh: Introduce --add option to add a dependency Jan Nieuwenhuizen
2008-08-13 16:20 ` Jonathan Nieder
2008-08-15 8:10 ` Jan Nieuwenhuizen [this message]
2008-08-15 15:25 ` Jonathan Nieder
2008-08-18 9:18 ` Jan Nieuwenhuizen
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=1218787834.7585.13.camel@heerbeest \
--to=janneke-list@xs4all.nl \
--cc=git@vger.kernel.org \
--cc=jrnieder@uchicago.edu \
--cc=kendy@suse.cz \
/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).