git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joey Hess <joey@kitenet.net>
To: git@vger.kernel.org
Subject: Re: finding unmerged branches
Date: Thu, 27 Aug 2009 22:08:26 -0400	[thread overview]
Message-ID: <20090828020826.GA28782@gnu.kitenet.net> (raw)
In-Reply-To: <20090827220241.GA1413@gnu.kitenet.net>

[-- Attachment #1: Type: text/plain, Size: 343 bytes --]

Joey Hess wrote:
> * Is this situation somewhat common, or an I doing something wrong?
>   (Assuming that I have a good reason to want to look at remote 
>   branches rather than waiting to get merge requests.)

Come to think, the github fork queue serves basically the same purpose,
but only for branches in github.

-- 
see shy jo

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2009-08-28  2:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-27 22:02 finding unmerged branches Joey Hess
2009-08-27 22:22 ` Avery Pennarun
2009-08-28  0:54   ` Joey Hess
2009-08-27 22:35 ` Björn Steinbrink
2009-08-27 23:25   ` Junio C Hamano
2009-08-28  0:44   ` Joey Hess
2009-08-28  2:08 ` Joey Hess [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=20090828020826.GA28782@gnu.kitenet.net \
    --to=joey@kitenet.net \
    --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).