git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: GIT 1.6.3-rc2 is out but...
Date: Sat, 25 Apr 2009 09:29:13 -0700	[thread overview]
Message-ID: <7vmya4zoh2.fsf@gitster.siamese.dyndns.org> (raw)

As a quick reminder, I tagged 1.6.3-rc2 and pushed it out last night, but
I forgot to apply a handful of patches I already had in my "ready to be
tested and queued" mailbox before doing so, so 1.6.3-rc3 will likely to
follow it before the next week begins.

Currently I have these tentatively queued on top of 1.6.3-rc2:

    Add an option not to use link(src, dest) && unlink(src) when that is unreliable
    connect: replace inet_ntop with getnameinfo
    Documentation: git-clean: make description more readable
    Documentation: git-clean: fix minor grammatical errors
    Remove obsolete bug warning in man git-update-server-info
    t7700-repack: repack -a now works properly, expect success from test
    t9001: use older Getopt::Long boolean prefix '--no' rather than '--no-'
    progress bar: round to the nearest instead of truncating down

                 reply	other threads:[~2009-04-25 16:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=7vmya4zoh2.fsf@gitster.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;
as well as URLs for NNTP newsgroup(s).