From: Petr Baudis <pasky@ucw.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: "Adam J. Richter" <adam@yggdrasil.com>,
torvalds@osdl.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Re: Re: Re: Re: GIT license (Re: Re: Re: Re: Re: [ANNOUNCE] git-pasky-0.1)
Date: Tue, 12 Apr 2005 21:29:24 +0200 [thread overview]
Message-ID: <20050412192924.GA26542@pasky.ji.cz> (raw)
In-Reply-To: <20050412095048.GB22614@pasky.ji.cz>
Dear diary, on Tue, Apr 12, 2005 at 11:50:48AM CEST, I got a letter
where Petr Baudis <pasky@ucw.cz> told me that...
> Dear diary, on Tue, Apr 12, 2005 at 10:39:40AM CEST, I got a letter
> where Geert Uytterhoeven <geert@linux-m68k.org> told me that...
> > On Tue, 12 Apr 2005, Petr Baudis wrote:
> ..snip..
> > > Basically, when you look at merge(1) :
> > >
> > > SYNOPSIS
> > > merge [ options ] file1 file2 file3
> > > DESCRIPTION
> > > merge incorporates all changes that lead from file2 to file3
> > > into file1.
> > >
> > > The only big problem is how to guess the best file2 when you give it
> > > file3 and file1.
> >
> > That's either the point just before you started modifying the file, or your
> > last merge point. Sounds simple, but if your SCM system doesn't track merges,
> > your SOL...
>
> Well, yes, but the last merge point search may not be so simple:
>
> A --1---2----6---7
> B \ `-4-. /
> C `-3-----5'
>
> Now, when at 7, your last merge point is not 1, but 2.
...and this is obviously wrong, sorry. You would lose 3 this way.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
98% of the time I am right. Why worry about the other 3%.
next prev parent reply other threads:[~2005-04-12 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-12 1:20 Adam J. Richter
2005-04-12 1:42 ` Petr Baudis
2005-04-12 8:39 ` Geert Uytterhoeven
2005-04-12 9:50 ` Petr Baudis
2005-04-12 19:29 ` Petr Baudis [this message]
2005-04-12 21:01 ` Chris Friesen
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=20050412192924.GA26542@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=adam@yggdrasil.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®