All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Linus Torvalds 
	<public-torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@hugh.gmane.org>,
	Andrew Morton 
	<public-akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@hugh.gmane.org>,
	Linux Kernel Mailing List 
	<public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org>,
	public-linux-usb-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org
Subject: Re: [GIT PATCH] USB fixes for 2.6.28-git
Date: Mon, 24 Nov 2008 20:20:51 -0800	[thread overview]
Message-ID: <20081125042051.GA17345@suse.de> (raw)
In-Reply-To: <7vprkklaob.fsf@gitster.siamese.dyndns.org>




On Mon, Nov 24, 2008 at 07:57:40PM -0800, Junio C Hamano wrote:
> 
> 
> Greg KH <gregkh-l3A5Bk7waGM@public.gmane.org> writes:
> 
> > On Thu, Nov 20, 2008 at 01:23:51PM -0800, Linus Torvalds wrote:
> >> 
> >> 
> >> On Wed, 19 Nov 2008, Greg KH wrote:
> >> > 
> >> > Please pull from:
> >> > 	master.kernel.org:/pub/scm/linux/kernel/git/gregkh/usb-2.6.git/
> >> 
> >> "Already up-to-date". 
> >> 
> >> I think you forgot to actually push them out.
> >
> > Crap, you're right, they are now there, sorry about that.
> 
> I've been wondering if git can do something to avoid things like this.
> 
> For example, if you push into a particular branch of a particular
> repository _only_ to ask Linus to pull and for no other purpose, one
> possible solution may be to trigger a hook on the receiving end of your
> push (i.e. the public repository Linus is asked to pull from) to send out
> the "Please pull from" message (I presume this would be a no-go as there
> is not much room for you to customize the message).
> 
> Alternatively, we may want to give an option to git-request-pull to
> actually run "git push" to the destination.
> 
> Thoughts?  Is it "none of Git's business"?

In this case, it was just my fault.  I just forgot to push the tree.  I
have my own scripts that I use to create my "please pull" message, that
don't really tie into git's infrastructure and I don't know if I would
want them to either.

thanks,

greg k-h



  reply	other threads:[~2008-11-25  4:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-20  5:50 [GIT PATCH] USB fixes for 2.6.28-git Greg KH
2008-11-20 21:23 ` Linus Torvalds
2008-11-20 21:48   ` Greg KH
2008-11-25  3:57     ` Junio C Hamano
2008-11-25  4:20       ` Greg KH [this message]
     [not found]       ` <20081125042051.GA17345__32159.7253824168$1227588787$gmane$org@suse.de>
2008-11-25  7:18         ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2008-12-01  6:16 Greg KH

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=20081125042051.GA17345@suse.de \
    --to=gregkh@suse.de \
    --cc=gitster@pobox.com \
    --cc=public-akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@hugh.gmane.org \
    --cc=public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
    --cc=public-linux-usb-u79uwXL29TY76Z2rM5mHXA@hugh.gmane.org \
    --cc=public-torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@hugh.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.