From: Sverre Rabbelier <srabbelier@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git 1.7.0.rc1
Date: Sun, 31 Jan 2010 02:12:19 +0100 [thread overview]
Message-ID: <fabb9a1e1001301712h3223f4c5xcf4742cde1642dfe@mail.gmail.com> (raw)
In-Reply-To: <7vaavvi4r5.fsf@alter.siamese.dyndns.org>
Heya,
Feel free to tell me "go build 1.7.0.rc0 yourself and see" to any of
these, but I can't right now, and am curious :).
On Sat, Jan 30, 2010 at 23:53, Junio C Hamano <gitster@pobox.com> wrote:
> * "git checkout A...B" is a way to detach HEAD at the merge base between
> A and B.
Does 'git checkout -b mergebase-a-b A...B' work as expected?
> * "git log" and friends learned "--glob=heads/*" syntax that is a more
> flexible way to complement "--branches/--tags/--remotes".
Not --glob=refs/*?
> * "git rebase --onto A...B" means the history is replayed on top of the
> merge base between A and B.
Oh wow, neat, I guess that complements the 'git checkout A...B'
behavior? Is there anywhere else that we could/should support this new
syntax, but don't?
> * "git rebase -i" also learned --autosquash option, that is useful
> together with the new "fixup" action.
Did we add a config option for this?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-01-31 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 22:53 [ANNOUNCE] Git 1.7.0.rc1 Junio C Hamano
2010-01-31 1:12 ` Sverre Rabbelier [this message]
2010-01-31 7:56 ` Ilari Liusvaara
2010-01-31 3:52 ` Anders Kaseorg
2010-01-31 7:32 ` Jeff King
2010-01-31 8:03 ` Junio C Hamano
2010-01-31 9:14 ` Jeff King
2010-01-31 19:23 ` Junio C Hamano
2010-01-31 9:36 ` Matthieu Moy
2010-01-31 18:28 ` Junio C Hamano
2010-02-01 18:09 ` [PATCH] Updates for dirty submodules in release notes and user manual Jens Lehmann
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=fabb9a1e1001301712h3223f4c5xcf4742cde1642dfe@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).