consider raising your voice for having a "guide_to_the_source.txt" set up -
it would help enormously - seeing especially how msysgit lacks commiters
On Sunday, June 16, 2013 8:14:35 PM UTC+3, Philip Oakley wrote:
> The main sub-commands which have beeen coded in c are in the sub-directory
> Try one of the short ones such as 'write-tree.c' which shows the setting
> up of the command line structure, and then goes and executes
> ret = write_cache_as_tree(sha1, flags, prefix);
> read-tree.c is a bit longer but also has the obvious #includes to
> It's a bit like peeling an onion - don't rub your eyes too soon ;-)
> ----- Original Message -----
> *From:* the....@gmail.com
> *To:* git-...@googlegroups.com
> *Cc:* the....@gmail.com ; Philip Oakley
> *Sent:* Sunday, June 16, 2013 4:57 PM
> *Subject:* Re: [git-users] developers docs ?
> Thanks - so a starting point would be git.c
> Where are the data structures defined ? The "objects" ?
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.3345 / Virus Database: 3199/6414 - Release Date: 06/15/13
On Sunday, June 16, 2013 3:41:37 PM UTC+3, the....@gmail.com wrote:
> I am curious to have a look at the source<https://github.com/msysgit/git/>.
> But since it is a rather big project I wonder is there a
> guide/walk-through to the structure of the source ?
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
For more options, visit https://groups.google.com/groups/opt_out.