From: Martin von Zweigbergk <martin.von.zweigbergk@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2011, #04; Wed, 23)
Date: Wed, 23 Mar 2011 20:39:09 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1103232015390.30954@debian> (raw)
In-Reply-To: <7v62r9csqr.fsf@alter.siamese.dyndns.org>
On Wed, 23 Mar 2011, Junio C Hamano wrote:
> --------------------------------------------------
> [Stalled]
>
> ...
>
> * mz/rebase (2011-02-28) 34 commits
> - rebase: define options in OPTIONS_SPEC
> (merged to 'next' on 2011-02-25 at 52caa7a)
> + Makefile: do not install sourced rebase scripts
> (merged to 'next' on 2011-02-22 at 3219155)
> + rebase: use @{upstream} if no upstream specified
> ...
>
> I think the tip one is a response to J6t's regression concerns; it looked
> Ok to me.
Do I need to do anything to un-stall (the tip of) this topic?
I didn't remove USAGE and LONG_USAGE in that patch because I wasn't
sure if they are used somehow. As far as I can see, they are only used
if no OPTIONS_SPEC is defined. If someone can confirm that, I can
submit an updated version.
And yes, it is a response to J6t's regression concerns.
/Martin
next prev parent reply other threads:[~2011-03-24 0:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 23:38 What's cooking in git.git (Mar 2011, #04; Wed, 23) Junio C Hamano
2011-03-24 0:39 ` Martin von Zweigbergk [this message]
2011-03-24 5:24 ` Junio C Hamano
2011-03-24 3:47 ` Nguyen Thai Ngoc Duy
2011-03-24 7:30 ` Junio C Hamano
2011-03-24 7:35 ` [PATCH 1/2] merge: match the help text with the documentation Junio C Hamano
2011-03-24 7:39 ` [PATCH 2/2] merge: merge with the default upstream with no argument Junio C Hamano
2011-05-05 14:05 ` Felipe Contreras
2011-05-05 17:33 ` Junio C Hamano
2011-05-05 20:26 ` Felipe Contreras
2011-03-24 8:00 ` What's cooking in git.git (Mar 2011, #04; Wed, 23) 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=alpine.DEB.2.00.1103232015390.30954@debian \
--to=martin.von.zweigbergk@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