Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: Re: 1.7.7-rc0 tagged and pushed out
Date: Fri, 26 Aug 2011 16:20:20 -0700	[thread overview]
Message-ID: <7vobzbbw0b.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <7vwrdzbwrt.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Fri, 26 Aug 2011 16:03:50 -0700")

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

> ... and I think I've collected all the recent leftover topics from the
> list that are at least going in the right direction if not perfect and
> queued them to update 'pu'.

Here is a preview of the "New Topics" section of the next "What's
cooking".


[New Topics]

* mg/maint-notes-C-doc (2011-08-25) 1 commit
 - git-notes.txt: clarify -C vs. copy and -F

* jc/clean-exclude-doc (2011-08-26) 1 commit
 - Documentation: clarify "git clean -e <pattern>"

* mh/check-ref-format-print-normalize (2011-08-25) 1 commit
 - check-ref-format --print: Normalize refnames that start with slashes

These tiny clean-up topics could go to 1.7.7 final. On the other hand,
they are not urgent, either.

* bk/ancestry-path (2011-08-25) 3 commits
 - revision: do not include sibling history in --ancestry-path output
 - revision: keep track of the end-user input from the command line
 - rev-list: Demonstrate breakage with --ancestry-path --all

The topic came up a bit too late in the cycle.

* mg/branch-list (2011-08-26) 5 commits
 - branch: allow pattern arguments
 - branch: introduce --list option
 - git-branch: introduce missing long forms for the options
 - git-tag: introduce long forms for the options
 - t6040: test branch -vv
 (this branch uses nk/branch-v-abbrev.)

The topic came up a bit too late in the cycle.

* mm/rebase-i-exec-edit (2011-08-26) 2 commits
 - rebase -i: notice and warn if "exec $cmd" modifies the index or the working tree
 - rebase -i: clean error message for --continue after failed exec

The topic came up a bit too late in the cycle.

* jk/default-attr (2011-08-26) 1 commit
 - attr: map builtin userdiff drivers to well-known extensions

I fixed up the test breakage just for fun, but this is not urgent.

* hv/submodule-merge-search (2011-08-26) 4 commits
 - submodule: Search for merges only at end of recursive merge
 - allow multiple calls to submodule merge search for the same path
 - submodule: Demonstrate known breakage during recursive merge
 - push: Don't push a repository with unpushed submodules
 (this branch uses fg/submodule-ff-check-before-push, fg/submodule-ff-check-before-push and jc/combine-diff-callback.)

The topic came up a bit too late in the cycle.
The bottom one needs to be replaced with a properly written commit log message.

* mm/mediawiki-as-a-remote (2011-08-26) 1 commit
 - Add a remote helper to interact with mediawiki (fetch & push)

Fun.

* nd/maint-autofix-tag-in-head (2011-08-26) 3 commits
 - Accept tags in HEAD or MERGE_HEAD
 - merge: remove global variable head[]
 - merge: keep stash[] a local variable

Probably needs a re-roll to aim a bit higher.

  reply	other threads:[~2011-08-26 23:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 23:03 1.7.7-rc0 tagged and pushed out Junio C Hamano
2011-08-26 23:20 ` Junio C Hamano [this message]
2011-08-30  2:32   ` Not yet 1.7.7-rc1 but Junio C Hamano
2011-08-31  0:59     ` Not yet 1.7.7-rc1 but... (take 2) 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

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

  git send-email \
    --in-reply-to=7vobzbbw0b.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    /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