From: Christian Couder <chriscool@tuxfamily.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jun 2009, #03; Sat, 27)
Date: Sun, 28 Jun 2009 15:50:38 +0200 [thread overview]
Message-ID: <200906281550.39051.chriscool@tuxfamily.org> (raw)
In-Reply-To: <7vy6rcg7hc.fsf@alter.siamese.dyndns.org>
On Sunday 28 June 2009, Junio C Hamano 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 branches, but I am still
> holding onto them.
Is there a reason why the following patches have been removed from pu:
commit 6dcab5fbeb56a8fdd908d54ae7154308bfa5f74b
Author: Christian Couder <chriscool@tuxfamily.org>
Date: Sun Jun 21 07:08:45 2009 +0200
rebase -i: use config file format to save author information
This is better than saving in a shell script, because it will make
it much easier to port "rebase -i" to C. This also removes some sed
regexps and some "eval"s.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
commit aac0a09aedae9dc3ca0e2c0bb5ad5f3918a821a5
Author: Christian Couder <chriscool@tuxfamily.org>
Date: Sun Jun 21 07:08:44 2009 +0200
rebase -i: remove get_author_ident_from_commit() from "git-sh-setup.sh"
The "get_author_ident_from_commit" function is only used in
"git-rebase--interactive.sh" so there is no need for this function
to be in "git-sh-setup.sh" anymore.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Thanks,
Christian.
next prev parent reply other threads:[~2009-06-28 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-28 7:09 What's cooking in git.git (Jun 2009, #03; Sat, 27) Junio C Hamano
2009-06-28 13:50 ` Christian Couder [this message]
2009-06-28 14:04 ` Johannes Schindelin
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=200906281550.39051.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--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).