git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhan Jianyu <nasa4836@gmail.com>
To: git@vger.kernel.org
Subject: Does Git now have any C struct version history tracking mechanism?
Date: Sun, 18 Aug 2013 18:33:12 +0800	[thread overview]
Message-ID: <CAHz2CGW_xR4Q193h2itCELdXEpoAxetj324ATstALHM03cSvFg@mail.gmail.com> (raw)

Hi, all.

* Background

  Such a requirement came into my mind when I am tracking a gloomy C
struct , with lengthy list of elements which are either elaborated or
opaque. So I use git blame to track it down and found that its
original version is quite simple and intuitive. So I think I could
just slice out every snapshot of this struct, reading every changelog
, to get a better knowledge of what it is and why it should be like
this.

It seems quite helpful but the process is quite cumbersome. So I
wonder if there is already some mechanism fulfilling my requirement in
Git.  If it doesn't,  would it be worthy adding one ?

Thanks




--

Regards,
Zhan Jianyu

             reply	other threads:[~2013-08-18 10:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-18 10:33 Zhan Jianyu [this message]
2013-08-19  5:54 ` Does Git now have any C struct version history tracking mechanism? Nazri Ramliy
2013-08-19  8:37   ` Thomas Rast
2013-08-20  3:55     ` Nazri Ramliy

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=CAHz2CGW_xR4Q193h2itCELdXEpoAxetj324ATstALHM03cSvFg@mail.gmail.com \
    --to=nasa4836@gmail.com \
    --cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).