From: Junio C Hamano <gitster@pobox.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2014, #03; Fri, 11)
Date: Fri, 11 Apr 2014 23:49:43 -0700 [thread overview]
Message-ID: <7v61mfm48o.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <53487a78f38bf_3b596b93106e@nysa.notmuch> (Felipe Contreras's message of "Fri, 11 Apr 2014 18:27:53 -0500")
Felipe Contreras <felipe.contreras@gmail.com> writes:
> Junio C Hamano wrote:
>> * fc/complete-aliased-push (2014-04-09) 1 commit
>> - completion: fix completing args of aliased "push", "fetch", etc.
>>
>> Will merge to 'next'.
>>
>>
>> * fc/remote-helper-fixes (2014-04-09) 4 commits
>> - remote-bzr: include authors field in pushed commits
>
> Before you do, you might want to pick the unrelated fix I just sent[1],
> otherwise this test might fail on some machines.
Will pick up $gmane/246157 (or at least will try to remember ;-).
Thanks.
>> - remote-bzr: add support for older versions
>> - remote-hg: always normalize paths
>> - remote-helpers: allow all tests running from any dir
>>
>> Will merge to 'next'.
>
>> * fc/publish-vs-upstream (2014-04-11) 8 commits
>> - sha1_name: add support for @{publish} marks
>> - sha1_name: simplify track finding
>> - sha1_name: cleanup interpret_branch_name()
>> - branch: display publish branch
>> - push: add --set-publish option
>> - branch: add --set-publish-to option
>> - Add concept of 'publish' branch
>> - t5516 (fetch-push): fix test restoration
>>
>> Add branch@{publish}; this round v3 hasn't yet seen much reviews
>> yet.
>>
>> Seems to have some interactions to break tests when merged to 'pu'.
>
> That was v2, wasn't it?
The tip d95807a0e1b7 (sha1_name: add support for @{publish} marks,
2014-04-11) is with timestamp "Fri Apr 11 12:59:11 2014 -0500",
which matches $gmane/246122, so I am reasonably sure that I applied
the v3 on the same base as the base I queued the v2 on, compared
them and then updated the branch. Also I can tell by seeing some
patches lost the retitle I did for the previous round.
next prev parent reply other threads:[~2014-04-12 6:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 22:22 What's cooking in git.git (Apr 2014, #03; Fri, 11) Junio C Hamano
2014-04-11 23:27 ` Felipe Contreras
2014-04-12 6:49 ` Junio C Hamano [this message]
2014-04-12 18:29 ` Ramsay Jones
2014-04-15 16:45 ` Junio C Hamano
2014-04-15 23:18 ` Duy Nguyen
2014-04-16 11:31 ` Ramsay Jones
2014-04-13 20:18 ` Michael Haggerty
2014-04-17 16:52 ` W. Trevor King
2014-04-17 17:52 ` 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=7v61mfm48o.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=felipe.contreras@gmail.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.
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).