git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pascal Obry <pascal@obry.net>
To: "Santi Béjar" <santi@agolina.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Finding the name of the parent branch?
Date: Fri, 30 Jan 2009 14:35:39 +0100	[thread overview]
Message-ID: <a2633edd0901300535mf2d9ceemd9e9009e0aa18b40@mail.gmail.com> (raw)
In-Reply-To: <adf1fd3d0901300516y3d1bf58dmda9c5172586d828@mail.gmail.com>

Santi,

> Maybe if you explain why you want it (a use case) instead of just this
> specific problem...

To know the proper merge base to display all commits done on a specific
topic branch.

>>> Just a counterexample, just rearranging you graph:
>>>
>>>                        o---B
>>>                        /
>>>                   o---2---o---o---o---C
>>>                  /
>>>          ---o---1---o---o---o---A
>>>
>>> From you description: For B I would get C and for C I would get A.
>
> Please, if you quote text do not edit it (the 1 and the 2 in this case).

Well I've just added 1 and 2, nothing changed in the semantic!

> Yes. Compare your sentence and mine:
>
> For B I want to get A and for C I want to get B.
> For B I would get C and for C I would get A.
>
> So for B you get A while I get C, and the equivalent for C.

Ok, that's expected since you have renamed B to C and C to B.

My tree was:


                        o---o---o---C
                        /
                   o---o---o---B
                  /
          ---o---o---o---o---o---A

Your's was:

                       o---B
                       /
                  o---o---o---o---o---C
                 /
         ---o---o---o---o---o---A

So when I said:

    For B I want to get A and for C I want to get B.

It is equivalent to your (just rename B and C).:

   For B I would get C and for C I would get A.

Frankly I do not see your point... That's maybe the cause of the
problem I'm having....

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|              http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595

  reply	other threads:[~2009-01-30 13:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-30 10:56 Finding the name of the parent branch? Pascal Obry
2009-01-30 11:18 ` Santi Béjar
2009-01-30 12:56   ` Pascal Obry
2009-01-30 13:16     ` Santi Béjar
2009-01-30 13:35       ` Pascal Obry [this message]
2009-01-30 13:57         ` Santi Béjar
2009-01-30 14:06           ` Pascal Obry
2009-01-30 14:46             ` Santi Béjar
2009-01-30 13:35     ` Michael J Gruber
2009-01-30 14:26 ` Thomas Koch
2009-01-30 15:58   ` Pascal Obry

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=a2633edd0901300535mf2d9ceemd9e9009e0aa18b40@mail.gmail.com \
    --to=pascal@obry.net \
    --cc=git@vger.kernel.org \
    --cc=santi@agolina.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.
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).