git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Santiago Torres <santiago@nyu.edu>
To: Fabio Aiuto <polinice83@libero.it>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Can't build first git commit
Date: Wed, 6 Mar 2019 15:39:11 -0500	[thread overview]
Message-ID: <20190306203910.xr2bwpqb3zrxnm63@LykOS.localdomain> (raw)
In-Reply-To: <1551903598.1727.3.camel@libero.it>

[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]

That was proably my bad. 

I still find it somewhat astounding that it compiles with a modern
toolchain after 15+ years. Many projects fail to do so (it's an
understandably high bar to have).

I'm glad this is possible and you were able to do so (maybe you want to
share your experiences about it somewhere? :))

Cheers!
-Santiago.


On Wed, Mar 06, 2019 at 09:19:58PM +0100, Fabio Aiuto wrote:
> Yes that's great.
> Why somebody told me about a outdate toolchain when I started this
> little thread about first git compiling? Sorry for my stupid question
> but the you just resolved with that make override...
> Maybe there's something I have to know?
> 
> Il giorno mer, 06/03/2019 alle 15.03 -0500, Jeff King ha scritto:
> > On Wed, Mar 06, 2019 at 08:58:40PM +0100, Fabio Aiuto wrote:
> > 
> > > Yes the fetch command wasn't written at that time, right? I didn't
> > > understand why should be better to work with the git code from
> > > github.
> > > There's something I misunderstood?
> > 
> > I just mean that it is an interesting fact that modern Git and Git
> > v1.0
> > can still interact seamlessly over the network. I.e., you could still
> > collaborate with somebody using an ancient version of Git (hopefully
> > nobody is using v1.0, but logically it extends to all of the
> > intermediate versions).
> > 
> > -Peff

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2019-03-06 21:44 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
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 [this message]
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190306203910.xr2bwpqb3zrxnm63@LykOS.localdomain \
    --to=santiago@nyu.edu \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=polinice83@libero.it \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).