All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Greg KH <gregkh@suse.de>
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 23:18:55 -0800	[thread overview]
Message-ID: <7v3ahgl1cw.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20081125042051.GA17345__32159.7253824168$1227588787$gmane$org@suse.de> (Greg KH's message of "Mon, 24 Nov 2008 20:20:51 -0800")



Greg KH <gregkh@suse.de> writes:

> 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:
>> >> ...
>> >> "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.
>> ...
> 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.

Oh, I wouldn't question that it was ultimately _your_ fault, but:

 (1) I see Linus mention "did you forget to push" every once in a while
     on this list (e.g. http://tinyurl.com/forgot-to-push); and

 (2) You are not the only person who sends "please pull" request and
     pushes out what needs to be pulled, and forgets to push.  Everybody
     who asks Linus to pull either needs to roll his own scripts.  This is
     wasteful, but this is partly git's fault, and something we could
     improve, because I do not think there is no usable canned tools that
     come with git that allows you to prepare a custom "please pull"
     message and helps you not to forget pushing out; and

 (3) As an early adopter who has his own wrappers around git that are
     tailored to match his own needs in this part of the workflow, you'd
     be an ideal source of requirements _if_ we would want to provide a
     usable canned tool for doing this.

Hence my comments.


  parent reply	other threads:[~2008-11-25  7:19 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
     [not found]       ` <20081125042051.GA17345__32159.7253824168$1227588787$gmane$org@suse.de>
2008-11-25  7:18         ` Junio C Hamano [this message]
  -- 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=7v3ahgl1cw.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=gregkh@suse.de \
    --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.