git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Erik Faye-Lund <kusmabite@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)
Date: Sun, 5 Dec 2010 14:00:43 +0100	[thread overview]
Message-ID: <AANLkTimX215CNAG_mosqzOh-EPBoSimK0s-n4YmKm1rb@mail.gmail.com> (raw)
In-Reply-To: <7voc90wx36.fsf@alter.siamese.dyndns.org>

On Sun, Dec 5, 2010 at 7:30 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Here are the topics that have been cooking.  Commits prefixed with '-' are
> only in 'pu' while commits prefixed with '+' are in 'next'.  The ones
> marked with '.' do not appear in any of the integration branches, but I am
> still holding onto them.
>
> --------------------------------------------------
> [New Topics]
>
> * aa/status-hilite-branch (2010-11-18) 1 commit
>  - status: show branchname with a configurable color
>
> I am indifferent/uninterested; I don't see anything wrong with it, but I
> do not find coloring the field particularly useful myself.
>
> * ef/help-cmd-prefix (2010-11-26) 2 commits
>  - (jc) review comments
>  - help: always suggest common-cmds if prefix of cmd
>
> Reroll, or squash?

I was planning on re-rolling, but looking at it with fresh eyes it
doesn't seem like there's much useful I can do. So feel free to just
squash it. I think the original commit message still makes sense.

  parent reply	other threads:[~2010-12-05 13:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05  6:30 What's cooking in git.git (Dec 2010, #01; Sat, 4) Junio C Hamano
2010-12-05  7:39 ` Jeff King
2010-12-05 19:54   ` Junio C Hamano
2010-12-06  0:54     ` aleksi.aalto
2010-12-09 17:27     ` Jeff King
2010-12-10 19:55       ` Junio C Hamano
2010-12-05 10:13 ` Yann Dirson
2010-12-05 20:23   ` Junio C Hamano
2010-12-06  7:29     ` Yann Dirson
2010-12-06  8:13       ` Miles Bader
2010-12-06  8:21         ` Yann Dirson
2010-12-06  8:39           ` Miles Bader
2010-12-06  8:48             ` Yann Dirson
2010-12-06  9:13               ` Miles Bader
2010-12-06 11:31                 ` Yann Dirson
2010-12-06 11:37                 ` Matthieu Moy
2010-12-10 21:59                 ` Junio C Hamano
2010-12-05 12:36 ` aleksi.aalto
2010-12-05 15:51   ` Patrick Rouleau
2010-12-05 13:00 ` Erik Faye-Lund [this message]
2010-12-05 20:15   ` Junio C Hamano
2010-12-05 15:00 ` Michael J Gruber
2010-12-05 20:06   ` Junio C Hamano
2010-12-06  8:55     ` Michael J Gruber
2010-12-06 15:39       ` Thiago Farina
2010-12-08 11:23 ` t9010 broken in pu [Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)] Thomas Rast
2010-12-08 11:28   ` Jonathan Nieder

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=AANLkTimX215CNAG_mosqzOh-EPBoSimK0s-n4YmKm1rb@mail.gmail.com \
    --to=kusmabite@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).