Git development
 help / color / mirror / Atom feed
From: "Santi Béjar" <santi@agolina.net>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Brian Foster" <brian.foster@innova-card.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [PATCH 4/4] Add support for 'namespace' history simplification
Date: Mon, 3 Nov 2008 22:45:16 +0100	[thread overview]
Message-ID: <adf1fd3d0811031345j4582e109jaf95aede0f33eff7@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0811031139520.3419@nehalem.linux-foundation.org>

On Mon, Nov 3, 2008 at 8:43 PM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> From: Linus Torvalds <torvalds@linux-foundation.org>
> Date: Mon, 3 Nov 2008 11:25:46 -0800
> Subject: [PATCH 4/4] Add support for 'namespace' history simplification
>
> Maybe this is mis-named, but what it does is to simplify history not by
> the contents of the tree, but whether a commit has been named (ie it's
> referred to by some branch or tag) or not.

Maybe --simplify-refs, or --simplify-overview.

>
> This makes it possible to see the relationship between different named
> commits, without actually seeing any of the details.
>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> ---
>
> This is the actual real meat of the logic, and it's really trivial. The
> actual code is really just a simple
>
>    if (simplify-by-namespace)
>        return lookup_decoration(..) ? REV_TREE_DIFFERENT : REV_TREE_SAME;

I tried it once, but I had problems simplifying the merges, and it is trivial...

Not that it matters a lot, but if you try it on master you get some
extra merges without a ref like:

373a273 (Merge git-gui 0.11.0, 2008-08-17)
f44bc33 (Sync with 1.5.6.5, 2008-08-06)

Thanks,
Santi

  reply	other threads:[~2008-11-03 21:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 13:39 [Q] Abbreviated history graph? Brian Foster
2008-11-03 14:20 ` Santi Béjar
2008-11-03 14:55   ` Santi Béjar
2008-11-03 15:46   ` Brian Foster
2008-11-03 16:08     ` Santi Béjar
2008-11-03 19:32 ` Linus Torvalds
2008-11-03 19:33   ` [PATCH 1/4] Add a 'source' decorator for commits Linus Torvalds
2008-11-03 19:35     ` [PATCH 2/4] revision: make tree comparison functions take commits rather than trees Linus Torvalds
2008-11-03 19:39       ` [PATCH 3/4] Make '--decorate' set an explicit 'show_decorations' flag Linus Torvalds
2008-11-03 19:43         ` [PATCH 4/4] Add support for 'namespace' history simplification Linus Torvalds
2008-11-03 21:45           ` Santi Béjar [this message]
2008-11-03 22:05             ` Linus Torvalds
2008-11-03 22:34               ` Santi Béjar
2008-11-03 22:28           ` Robin Rosenberg
2008-11-04 21:33           ` Clemens Buchacher
2008-11-03 20:15   ` [Q] Abbreviated history graph? Linus Torvalds
2008-11-03 20:34     ` Linus Torvalds
2008-11-04  8:45     ` Junio C Hamano

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=adf1fd3d0811031345j4582e109jaf95aede0f33eff7@mail.gmail.com \
    --to=santi@agolina.net \
    --cc=brian.foster@innova-card.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=torvalds@linux-foundation.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