From: Fabio Aiuto <polinice83@libero.it>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Can't build first git commit
Date: Wed, 06 Mar 2019 21:19:58 +0100 [thread overview]
Message-ID: <1551903598.1727.3.camel@libero.it> (raw)
In-Reply-To: <20190306200356.GB23315@sigill.intra.peff.net>
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
next prev parent reply other threads:[~2019-03-06 20:20 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 [this message]
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=1551903598.1727.3.camel@libero.it \
--to=polinice83@libero.it \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.