All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Git List <git@vger.kernel.org>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
	Johannes Sixt <j.sixt@viscovery.net>,
	Yann Dirson <dirson@bertin.fr>,
	Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: Itches with the current rev spec
Date: Mon, 29 Apr 2013 21:02:19 -0700	[thread overview]
Message-ID: <7vip34fyyc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vobcxl3ui.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Mon, 29 Apr 2013 09:05:25 -0700")

Junio C Hamano <gitster@pobox.com> writes:

> A much larger issue is that the current setup_revisions()
> infrastructure does not let us express an operation that involves
> two or more DAGs.  People sometimes wish to say an equivalent of
>
>     git show $(git rev-list A..B) $(git rev-list C..D)
>
> but obviously
>
>     git show A..B C..D
>
> is not the way to say it, and this limitation comes from it.

Just a clarification. Technically, this is _not_ impossible.  With
some (read: quite a lot of) work to move objects.flags out of the
object and to allow unbounded number of flag bits, you could support
arbitrary number of ranges that are UNION'ed together by pretty much
the same code structure as the current revision machinery.  You need
2 x N bits (for the above example, 2 x 2 bits) per commit.

I am not saying it is easy or we should start working on it, though
;-).

  parent reply	other threads:[~2013-04-30  4:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25  5:07 Itches with the current rev spec Ramkumar Ramachandra
2013-04-25  5:54 ` Ramkumar Ramachandra
2013-04-25  8:22 ` Matthieu Moy
2013-04-25  8:48   ` Felipe Contreras
2013-04-25 11:06     ` Ramkumar Ramachandra
2013-04-29 14:00   ` Michael J Gruber
2013-04-25  9:09 ` Andreas Schwab
2013-04-25  9:13   ` Ramkumar Ramachandra
2013-04-25 19:08 ` Phil Hord
2013-04-26  8:19 ` Yann Dirson
2013-04-26  8:43   ` Johannes Sixt
2013-04-26 12:33     ` Ramkumar Ramachandra
2013-04-26 17:49     ` Junio C Hamano
2013-04-26 19:48       ` Felipe Contreras
2013-04-26 21:13         ` Junio C Hamano
2013-04-29 15:08           ` Ramkumar Ramachandra
2013-04-29 15:37             ` Yann Dirson
2013-04-29 16:05             ` Junio C Hamano
2013-04-29 17:14               ` Ramkumar Ramachandra
2013-04-29 17:33                 ` Junio C Hamano
2013-04-29 19:10                   ` Ramkumar Ramachandra
2013-04-29 19:23               ` Ramkumar Ramachandra
2013-04-30  4:02               ` Junio C Hamano [this message]
2013-04-29 15:20           ` Ramkumar Ramachandra

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=7vip34fyyc.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=artagnon@gmail.com \
    --cc=dirson@bertin.fr \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.