git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abhishek Kumar <abhishekkumar8222@gmail.com>
To: git@vger.kernel.org
Cc: stolee@gmail.com, jnareb@gmail.com
Subject: [GSoC] Blog post on reachability queries
Date: Wed, 20 May 2020 22:07:22 +0530	[thread overview]
Message-ID: <20200520163653.GA76552@Abhishek-Arch> (raw)

Greetings everyone!

I am working on implementing Generation Number v2. I have written an
article about reachability queries, which I feel is necessary background
for understanding the project.

Here's the summary of article:
> Reachability refers to the ability to get from one vertex to another
> within a graph.
>
> Reachability queries are an interesting problem, improving performance
> for many graph operations. Better and more sophisticated solutions are
> being created as the size of working graphs keeps increasing.
>
> Reachability for the undirected graph can be found in linear
> preprocessing and constant query time with disjoint set unions. The
> answer isn't as evident for a directed graph because of differing
> performance on positive and negative queries, nature and size of graph
> and other factors. Topological Levels, Post Order DFS Intervals and
> Contraction Hierachies are some of the building blocks for such
> algorithms.

In a later article, I will talk about the specifics of generation number
for Git. In particular, how Git uses reachability queries, the need for
Generation Number v2 i.e., _Correted Commit Date With Strictly Monotonic
Offset_ and other interesting tidbits I come across.

You can find the article here:

https://abhishekkumar2718.github.io/programming/2020/05/20/reachability-queries.html

I appreciate any suggestions or feedback.

Thanks
Abhishek

             reply	other threads:[~2020-05-20 16:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 16:37 Abhishek Kumar [this message]
2020-05-21 14:16 ` [GSoC] Blog post on reachability queries jnareb

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=20200520163653.GA76552@Abhishek-Arch \
    --to=abhishekkumar8222@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=stolee@gmail.com \
    /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).