All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2010, #01; Tue, 9)
Date: Tue, 09 Nov 2010 21:19:27 +0100	[thread overview]
Message-ID: <vpqd3qe5jxs.fsf@bauges.imag.fr> (raw)
In-Reply-To: <7vbp5ymfyo.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Tue\, 09 Nov 2010 11\:53\:19 -0800")

Junio C Hamano <gitster@pobox.com> writes:

> * mm/phrase-remote-tracking (2010-11-02) 10 commits
>  - git-branch.txt: mention --set-upstream as a way to change upstream configuration
>  - user-manual: remote-tracking can be checked out, with detached HEAD
>  - user-manual.txt: explain better the remote(-tracking) branch terms
>  - Change incorrect "remote branch" to "remote tracking branch" in C code
>  - Change incorrect uses of "remote branch" meaning "remote-tracking"
>  - Change "tracking branch" to "remote-tracking branch"
>  - everyday.txt: change "tracking branch" to "remote-tracking branch"
>  - Change remote tracking to remote-tracking in non-trivial places
>  - Replace "remote tracking" with "remote-tracking"
>  - Better "Changed but not updated" message in git-status
>
> Is everybody happy with this round?  I'd prefer to merge it to 'next' or
> even 'master' and have further polishing be done, if necessary,
> in-tree.

The version in pu is the right one (I have to admin I did not make the
task easy ;-), thanks. I didn't get comment for a while, so I guess
it's OK for next, or master if you want.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

  parent reply	other threads:[~2010-11-09 20:21 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-09 19:53 What's cooking in git.git (Nov 2010, #01; Tue, 9) Junio C Hamano
2010-11-09 20:11 ` Ævar Arnfjörð Bjarmason
2010-11-09 20:19 ` Matthieu Moy [this message]
2010-11-09 20:29   ` Drew Northup
2010-11-09 20:38 ` Jonathan Nieder
2010-11-09 21:38 ` Jakub Narebski
2010-11-11 17:21   ` Junio C Hamano
2010-11-11 23:53     ` Jakub Narebski
2010-11-09 21:46 ` Johan Herland
2010-11-09 22:11 ` Jeff King
2010-11-09 22:17 ` Erik Faye-Lund
2010-11-09 22:21   ` Ævar Arnfjörð Bjarmason
2010-11-09 22:25     ` Erik Faye-Lund
2010-11-09 22:27       ` Ævar Arnfjörð Bjarmason
2010-11-10 20:35   ` Yann Dirson
2010-11-11 12:26 ` Nguyen Thai Ngoc Duy
2010-11-11 14:28 ` Nguyen Thai Ngoc Duy
2010-11-14 13:02 ` [PATCH] use persistent memory for rejected paths Clemens Buchacher
2010-11-15 18:31   ` Junio C Hamano
2010-11-15 19:02     ` Clemens Buchacher
2010-11-15 19:03   ` Matthieu Moy
2010-11-15 19:41     ` Clemens Buchacher
2010-11-15 19:52       ` [PATCH v2] " Clemens Buchacher
2010-11-16 16:41         ` Matthieu Moy
2010-11-15 23:05       ` [PATCH] " Junio C Hamano
2010-11-15 23:30         ` Clemens Buchacher

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=vpqd3qe5jxs.fsf@bauges.imag.fr \
    --to=matthieu.moy@grenoble-inp.fr \
    --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 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.