lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 24 Nov 2008 20:20:51 -0800
From:	Greg KH <gregkh@...e.de>
To:	Junio C Hamano <gitster@...ox.com>
Cc:	Linus Torvalds 
	<public-torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@...h.gmane.org>,
	Andrew Morton 
	<public-akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@...h.gmane.org>,
	Linux Kernel Mailing List 
	<public-linux-kernel-u79uwXL29TY76Z2rM5mHXA@...h.gmane.org>,
	public-linux-usb-u79uwXL29TY76Z2rM5mHXA@...h.gmane.org
Subject: Re: [GIT PATCH] USB fixes for 2.6.28-git




On Mon, Nov 24, 2008 at 07:57:40PM -0800, Junio C Hamano wrote:
> 
> 
> Greg KH <gregkh-l3A5Bk7waGM@...lic.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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists