From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Jörg Sommer" <joerg@alea.gnuu.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] Fix t3404 assumption that `wc -l` does not use whitespace.
Date: Mon, 28 Apr 2008 19:07:57 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0804281902040.19187@eeepc-johanness> (raw)
In-Reply-To: <20080428163003.GA6449@alea.gnuu.de>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 2512 bytes --]
Hi,
On Mon, 28 Apr 2008, Jörg Sommer wrote:
> Johannes Schindelin schrieb am Mon 28. Apr, 14:42 (+0100):
> > On Mon, 28 Apr 2008, Jörg Sommer wrote:
> > > Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > > > On Sun, 27 Apr 2008, Junio C Hamano wrote:
> > > >
> > > >> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> > > >>
> > > >> > ... It did not help that I hated the fact that that series changed
> > > >> > the original design without even understanding it.
> > > >>
> > > >> Care to elaborate on this point further? I do not get it.
> > > >
> > > > The original implementation of -p was modeled closely after
> > > > filter-branch, in that it created a subdirectory (dotest/rewritten)
> > > > containing the new commit names for those commits that were rewritten.
> > >
> > > But that wasn't the way rebase -i works.
> >
> > I know exactly how it works. D'oh.
> >
> > > You had to jump in before pick_one does anything which clearly shows you
> > > did something different from the default way.
> >
> > That is bullshit. I did not do anything "different from the default way".
> > I carefully designed an interface that was easy to understand, because it
> > mimicked how you would do the same _by hand_, but without the hassle to
> > actually having to do everything by hand.
> >
> > In other words, rebase -i is just a cherry-pick in a loop.
>
> But not rebase -i -p.
Yes. With the exception that you have to checkout and merge in the loop,
too.
> > And _exactly_ the same should have been done for -p.
>
> But you didn't do it.
Very well done. If your intention is to piss me off: you succeeded.
_OF COURSE_ I did not do it. That is why it was not working.
But you could have fixed that.
Instead, you chose to complicate things.
> > Namely, _not_ introduce some artificial marks, but use the _commit
> > names_!
>
> I don't buy, you don't use marks (notes on paper or git tags) when you
> rebase a branch with at least 8 commits and 2 merges.
>
> And Junio discribed how he would do such a rebase and it included marks.
> And I follow how. So no, they aren't artificial.
So you again ignored completely the argument I made.
Brilliant.
The same issue is _totally_ the same _without_ -p!
And you cannot fix the problem by introducing another one.
You can try to complicate things even further, sure, but you will not
change the fact that this is no solution at all.
Well, I refuse to let you insult my intelligence any more.
Ciao,
Dscho
next prev parent reply other threads:[~2008-04-28 18:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-27 15:16 [PATCH 2/2] Fix t3404 assumption that `wc -l` does not use whitespace Brian Gernhardt
2008-04-27 15:22 ` Johannes Schindelin
2008-04-27 15:32 ` Brian Gernhardt
2008-04-28 9:41 ` Jeff King
2008-04-28 9:56 ` Mike Ralphson
2008-05-13 9:11 ` Jeff King
2008-05-13 18:10 ` Mike Ralphson
2008-05-15 10:16 ` Mike Ralphson
2008-05-15 11:20 ` Jeff King
2008-05-15 11:23 ` Jeff King
2008-05-15 17:18 ` Junio C Hamano
2008-05-16 14:22 ` Mike Ralphson
2008-04-28 12:40 ` Brian Gernhardt
2008-04-27 17:31 ` Junio C Hamano
2008-04-28 10:13 ` Johannes Schindelin
2008-04-28 11:40 ` Jörg Sommer
2008-04-28 13:42 ` Johannes Schindelin
2008-04-28 16:30 ` Jörg Sommer
2008-04-28 18:07 ` Johannes Schindelin [this message]
2008-04-28 16:19 ` Junio C Hamano
2008-04-28 18:01 ` Johannes Schindelin
2008-04-28 21:24 ` Junio C Hamano
2008-04-28 21:30 ` Johannes Schindelin
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.0804281902040.19187@eeepc-johanness \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=joerg@alea.gnuu.de \
/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