git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2012, #03; Tue, 13)
Date: Tue, 13 Nov 2012 12:01:05 -0800	[thread overview]
Message-ID: <7vbof1e0hq.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20121113175205.GA26960@sigill.intra.peff.net> (Jeff King's message of "Tue, 13 Nov 2012 12:52:06 -0500")

Jeff King <peff@peff.net> writes:

> This is my final "what's cooking" as interim maintainer. I didn't
> graduate anything to master, but I updated my plans for each topic to
> give Junio an idea of where I was.

After exploding the first-parent history between your master..pu
into component topics and recreating one new merge-fix for
nd/wildmatch topic, I think I now know how to rebuild your
integration branches.

I still haven't caught up with the past discussions (and still am
slightly jetlagged), but I think I can take it over from here with
help from contributors.

Thanks.

  reply	other threads:[~2012-11-13 20:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-13 17:52 What's cooking in git.git (Nov 2012, #03; Tue, 13) Jeff King
2012-11-13 20:01 ` Junio C Hamano [this message]
2012-11-13 20:45 ` Torsten Bögershausen
2012-11-13 20:48   ` Pyeron, Jason J CTR (US)
2012-11-14  1:18   ` Mark Levedahl
2012-11-14 19:02     ` Jeff King
2012-11-14 21:13       ` Torsten Bögershausen
2012-11-15  0:16         ` Jeff King
2012-11-15  0:19           ` Junio C Hamano
2012-11-15  1:50           ` Mark Levedahl
2012-11-15  1:56             ` Jeff King
2012-11-15  5:54               ` Torsten Bögershausen
2012-11-16 18:52                 ` Junio C Hamano
2012-11-17  7:11                   ` Torsten Bögershausen
2012-11-15 19:05   ` Ramsay Jones
2012-11-15 19:35     ` Torsten Bögershausen
2012-11-15 23:34       ` Mark Levedahl
2012-11-13 22:57 ` Junio C Hamano

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vbof1e0hq.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).