From: "Shawn O. Pearce" <spearce@spearce.org>
To: Francis Moreau <francis.moro@gmail.com>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Teach git-describe to display distances from tags.
Date: Fri, 26 Jan 2007 04:51:14 -0500 [thread overview]
Message-ID: <20070126095114.GA15905@spearce.org> (raw)
In-Reply-To: <38b2ab8a0701260139w25d3e6c7ka8a0097f247f8421@mail.gmail.com>
Francis Moreau <francis.moro@gmail.com> wrote:
> But there are incompatibilities.
Nothing really *that* major. Heck, that git-describe change is
probably one of the biggest, if not the biggest.
> Another example, which may be a bad one since I unfortunately don't
> have time to follow closely git's development: the internal of 'git
> pull' has completely changed. If I clone a repo with git v1.4.x and I
> pull in this repo with git v1.5.x, does it still works ?
Yes, of course. Just like before too.
What's different is if you clone with 1.5.x, as we now default to the
seperate remotes layout. This was an option in 1.4.x and earlier,
its now the only way its done in 1.5.x.
--
Shawn.
next prev parent reply other threads:[~2007-01-26 9:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 17:39 [PATCH 1/2] Teach git-describe to display distances from tags Shawn O. Pearce
2007-01-25 21:26 ` Junio C Hamano
2007-01-25 21:37 ` Shawn O. Pearce
2007-01-25 21:42 ` Junio C Hamano
2007-01-25 21:49 ` Shawn O. Pearce
2007-01-25 23:32 ` Nicolas Pitre
2007-01-26 0:13 ` Junio C Hamano
2007-01-26 8:52 ` Francis Moreau
2007-01-26 9:00 ` Junio C Hamano
2007-01-26 9:39 ` Francis Moreau
2007-01-26 9:51 ` Shawn O. Pearce [this message]
2007-01-26 10:36 ` Andy Parkins
2007-01-26 14:28 ` [PATCH] If abbrev is set to zero in git-describe, don't add the unique suffix Andy Parkins
2007-01-26 13:33 ` [PATCH 1/2] Teach git-describe to display distances from tags Jakub Narebski
2007-01-26 19:37 ` Matthias Lederhofer
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=20070126095114.GA15905@spearce.org \
--to=spearce@spearce.org \
--cc=francis.moro@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 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).