All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Fabio Aiuto <polinice83@libero.it>
Cc: Santiago Torres <santiago@nyu.edu>,
	git@vger.kernel.org, asymptosis <asymptosis@posteo.net>,
	Jeff King <peff@peff.net>
Subject: Re: Can't build first git commit
Date: Mon, 4 Mar 2019 14:25:59 -0800	[thread overview]
Message-ID: <20190304222559.GA112305@google.com> (raw)
In-Reply-To: <1551730792.4573.1.camel@libero.it>

Hi,

Fabio Aiuto wrote:

> What a pity, It would have been very useful for me, to debug around
> that simple version, to understand how everithing works.

Jeff King suggested how you can update the build command to get it
working.  In general, I think people sometimes overthink what is
involved in a build: something like

	cc *.c

plus appropriate warning, optimization, debug, -D, and library flags
should work just fine.

If you haven't already read it, I also recommend reading
https://www.kernel.org/pub/software/scm/git/docs/user-manual.html#hacking-git.
If you have ideas for improving the text there (perhaps with suggested
build instructions?), patches to Documentation/user-manual.txt are
very welcome.

Thanks and happy hacking,
Jonathan

  parent reply	other threads:[~2019-03-04 22:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 19:58 Can't build first git commit Fabio Aiuto
2019-03-04 20:10 ` Santiago Torres
2019-03-04 20:19   ` Fabio Aiuto
2019-03-04 20:22     ` Santiago Torres
2019-03-04 21:48     ` asymptosis
2019-03-04 22:25     ` Jonathan Nieder [this message]
2019-03-04 20:40 ` Jeff King
2019-03-05 18:42   ` Fabio Aiuto
2019-03-05 19:15   ` Jeff King
2019-03-06 19:58     ` Fabio Aiuto
2019-03-06 20:03       ` Jeff King
2019-03-06 20:19         ` Fabio Aiuto
2019-03-06 20:39           ` Santiago Torres
2019-03-06 21:54             ` Jeff King
2019-03-06 20:52         ` Fabio Aiuto
2019-03-06 21:57           ` Jeff King
     [not found]             ` <1551985495.1606.1.camel@libero.it>
2019-03-07 19:41               ` Jeff King
2019-03-07 20:07                 ` Fabio Aiuto

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=20190304222559.GA112305@google.com \
    --to=jrnieder@gmail.com \
    --cc=asymptosis@posteo.net \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=polinice83@libero.it \
    --cc=santiago@nyu.edu \
    /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.