From: nicolas.pouillard@gmail.com (Nicolas Pouillard)
Subject: [sup-talk] master branch merge report
Date: Tue, 08 Sep 2009 22:28:56 +0200 [thread overview]
Message-ID: <1252441390-sup-9847@peray> (raw)
In-Reply-To: <1252440062-sup-8543@masanjin.net>
Excerpts from William Morgan's message of Tue Sep 08 22:05:14 +0200 2009:
> Reformatted excerpts from Nicolas Pouillard's message of 2009-09-08:
> > Thanks for these reports on the status of branches. They are really
> > precious. May ask for more? :) I would like you to also report on the
> > status of what is merged in next (or not yet merged in master).
>
> The only branches not merged into master at this point are
> preemptive-loading and alignment-tweaks. This is based on a gut estimate
> of whether they need to bake a little longer.
OK nice.
> You can always get a complete report by using git wtf
> (http://git-wt-commit.rubyforge.org/git-wtf). `git wtf -r -s master` and
> `git wtf -r -s next` will show you what's merged into master and next
> respectively.
I already use git-wtf (thanks for this tool BTW), with still some pain though.
These two commands outputs ~60 lines about dozen of branches. However that's
mainly due to the fact that I do have private branches.
It would be nice to simply ask differences between to branches in terms of
merged branches: git wtf mainline/master..mainline/next
> I've also just merged custom-search-hook into master, with some effort.
Thanks
--
Nicolas Pouillard
http://nicolaspouillard.fr
prev parent reply other threads:[~2009-09-08 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 19:45 William Morgan
2009-09-08 19:51 ` Nicolas Pouillard
2009-09-08 20:05 ` William Morgan
2009-09-08 20:28 ` Nicolas Pouillard [this message]
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=1252441390-sup-9847@peray \
--to=nicolas.pouillard@gmail.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